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, and it discloses nothing: no read/write nature, no side effects, no auth or rate-limit notes, no output characteristics. The text is a bare identifier, so an agent learns nothing beyond the name.

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, but short due to under-specification rather than conciseness; it is a single fragmented label with no front-loaded explanation. Nothing in it earns its place beyond identifying the namespaced tool.

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?

For a tool with two parameters, a 6-value enum, and no annotations or output schema, the description provides nothing an agent needs to invoke it correctly. The intended scope, output, and relationship to ui.mode.recommend are all missing.

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 coverage is 50% — the enum 'focus' is fully enumerated in the schema but 'mode' only has the vague string description 'SDK-supported UI ownership mode.' The description adds zero meaning to either parameter, leaving the caller to guess valid mode values and how mode and focus interact.

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 is only 'MediaSFU React Native Expo :: ui.overrides.guide (ui-overrides).' — it restates the tool name and provides no verb or description of what the tool actually does. An agent cannot tell from this text whether it generates overrides guidance, lists override points, or validates an override config.

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 when-to-use guidance, no prerequisites, and no mention of any alternative. The sibling list contains ui.mode.recommend and shared::ui.overrides.guide, but the description gives no cue about which one to pick or when.

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