@neel platform-tools is a standalone package usable by itself. The reason they break it is because they don't check out the sources with repo and don't build it with the Android Open Source Project build system. They try to check out only a smaller set of repositories, build it with the distribution toolchain and link against system libraries potentially with missing features and bug fixes. They use their own build system, not the AOSP soong build system using ninja as a backend.
Some distributions also don't understand the AOSP release system and wrongly use OS stable release tags to build platform-tools. It's meant to be built from the platform-tools tags for the standalone stable release. It can be built from the OS tags but is only meant to be used for working with the specific OS version you built and you're better off using the latest platform-tools instead even when doing development work on a specific OS version.
You can build the individual tools if you want instead of platform-tools as a whole. They don't want to use the AOSP toolchain but they could replace that with their own without using their own build system. It would still be best to use the same toolchain revisions instead of a different one and to use the same libraries, etc. instead of trying to use different system ones. It's a typical Linux distribution problem.
It's also highly problematic that it gets frozen at an ancient version in Debian, etc. They have a development snapshot based on an Android 10 stable release which was not meant to be used for building standalone platform-tools. It's ancient and is half a year older than it seems since Android 10 didn't have the latest platform-tools code during the life of Android 10.