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: no indication of whether it reads or mutates state, whether it requires auth, what output it produces, or how overrides interact with an existing UI mode. For an unannotated tool this is a complete gap.

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 text is short, but it is under-specified rather than concise; a single identifier-style fragment conveys no information. Brevity here is a symptom of missing content, not efficient editing.

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, an unexplained enum parameter, and a two-parameter contract, the description should explain the override workflow and its relationship to UI modes. None of that is present, leaving the agent unable to call the tool 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 terse description while 'focus' has only an enum with no explanation of what the values mean or how they affect the guide. The description adds zero parameter meaning, so it fails to compensate for the coverage gap.

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 restatement of the tool name and namespace ('MediaSFU Vue :: ui.overrides.guide (ui-overrides)') with no verb describing what the tool actually does. It does not distinguish this from the sibling vue::ui.mode.recommend or shared::ui.overrides.guide. This is a tautology rather than a statement of 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 guidance on when to call this tool, when not to, or which sibling to use instead — notable given the near-identical vue::ui.mode.recommend and the shared::ui.overrides.guide alternatives. The agent must infer usage entirely from the name.

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