Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about what the tool does, whether it mutates state, requires auth, or has side effects. It is a bare title.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short to the point of being empty; there is no wasted text because there is no substantive content at all. This is under-specification, not conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, two params (one undescribed), and an enum left unexplained, the description is completely inadequate for an agent to know what this tool returns or how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: the 'mode' param has a description but 'focus' does not, and neither is explained in the description. The enum values (branding, layout, cards, controls, headless-shell, native-bridge) are left entirely undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the namespace-qualified name ("MediaSFU Android :: ui.overrides.guide (ui-overrides)") with no verb or resource statement. It is essentially a tautology that gives no hint of what the tool actually does or returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no indication of when to use this tool, when not to, or how it differs from siblings like android::ui.mode.recommend or shared::ui.overrides.guide. No alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.