a function that does not perform as advertised is a bug,
Unless it’s just poorly documented.
special knowledge by the initiated notwithstanding.
The simple fact is that a lot of Blender features and functions are poorly documented. Most, however, have probably been discussed at some point in this and other forums. If not, then such discussion can always be prompted with a question and this is one way to uncover true bugs.
Now, you’re certainly not the first to question Blender’s interface - entire threads have been dedicated to it - and you won’t be the last. However, your language is almost patronising and helpful people can quickly become unhelpful in that situation.
The reality is that the coders will code whatever they want to code and the documenters will document whatever they want to document. They do it for free so those of us who can’t code and those who aren’t confident with writing are usually grateful other people do it for them - though none of us is unwilling to suggest areas that might need attention. In fact, it’s usually welcome providing the criticism is constructive.
Blender is free but only in monetary terms. The real cost of Blender is research - and lots of it. Read, experiment, read more, experiment more, ask questions, read answers, make suggestions, read more. Oh, and read more and experiment a bit more and don’t expect to be proficient in a few weeks. When you find a solution you feel should have been easier to find, add something to the wiki docs. It won’t take a year to find some things that you feel you could document better than is currently the case. With a little more reading and experimenting you’ll be able to document the camera and tracking functions in a very short time.