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: not whether the tool reads or writes, whether it requires an SDK context, what it returns, or how 'override' semantics behave. The dotted name alone conveys zero behavioral information.

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?

The single line is short but that brevity reflects under-specification rather than conciseness. There is no front-loaded statement of purpose, inputs, or scope for an agent to anchor on.

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 two-parameter tool in a large namespace of near-identical sibling tools, with no annotations and no output schema, the description supplies none of the context needed to invoke it correctly. It is effectively empty.

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?

The schema has two parameters with only 50% description coverage ('mode' is described, the 'focus' enum values are not), and the description adds no parameter meaning whatsoever. With low coverage the description is expected to compensate, and it does not.

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 a bare restatement of the tool name and its dotted namespace ('mediasfu-shared :: ui.overrides.guide (ui-overrides)'), with no verb and no statement of what the tool actually does. An agent cannot tell what a 'UI overrides guide' produces or how it differs from the sibling ui.mode.recommend. This is a tautology rather than a purpose.

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 differentiation from siblings such as shared::ui.mode.recommend, shared::headless.integration.plan, or the per-platform ui.overrides.guide variants. Nothing tells the agent when this tool is the right choice.

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