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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the call is read-only, what it returns, what the 'mode' and 'focus' inputs actually change, or whether any side effects occur.

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 this is under-specification rather than conciseness — the single sentence is pure namespace restatement and carries no information. Brevity here costs the agent everything it needs to invoke the tool correctly.

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 with no annotations, no output schema, and an unexplained enum, the description is completely inadequate and omits everything an agent would need to call 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 only 50%: 'mode' has a one-line schema description while 'focus' has an enum but no explanation of what each value means. The description adds no parameter meaning at all, leaving the agent unable to interpret 'focus' values such as 'headless-shell' or 'native-bridge'.

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 tool name and namespace ('MediaSFU Kotlin :: ui.overrides.guide (ui-overrides)') with no verb or explanation of what the tool actually produces. It hints at a UI-overrides guide but does not say whether it returns documentation, generates code, or validates configuration, and gives no differentiation from the sibling ui.mode.recommend.

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 the closely related ui.mode.recommend tool or any alternative. An agent has no basis for choosing this tool over its siblings.

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