2. Good managers set direction and exist to acquire resources for the team and eliminate barriers out of the way of the team when they are headed in that direction. Their role is not to interrupt the team so that they can answer a question from upper management.
3. Most of half of urgent manager requests are due to lack of planning either on their part or on their manager's part. They knew they needed this information a few days ago, but felt "it's OK to interrupt the team when I really need it".
4. Most of the other half are due to their inability to push back.
5. There will be times when the managers do need information urgently. It is then their responsibility to accept the hit in productivity that it incurs.
I've worked with both good and bad managers. The good ones have these qualities.
That's why they are managers and not low level developers. Developer does not like it? Well, a developer can migrate to writing less code and caring more about business related stuff. It is not like those who can write serializer cannot figure if a certain fire drill is required based on the amount of $$ coming in from a customer who is affected by a bug/wants something.
You missed the part where the manager has to evaluate and push back if needed. If their primary role is merely to do what their bosses tell them to, then they are not doing any managing.
99% of the companies can replace 75% of the managers with supervisors ( foreman in constructions/manufacturing ) and get a better result. Most of the "teams" inside organizations dont need managers - they need supervisors as organization does not need to have mini fiefdoms.
You are missing the point of what a manager is.
Good managers know how to ship products by knowing how to manage knowledge workers and removing friction in the communication inside and outside the team.
Good managers ask when they actually need something and they expect those working for them to accommodate such requests immediately. That is why, after all, they are managers.