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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not whether it is read-only, what it returns, what permissions it needs, or how the recommendation is computed. A pure identifier string gives zero behavioral signal.

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 fragment conveys no task information. Brevity here is a defect, not an efficiency.

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 parameterized advisory tool with no annotations and no output schema, the description should explain the inputs and the shape of the guidance returned. It supplies neither, leaving the agent unable to call the tool with confidence.

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 0% for two parameters (ownershipLevel, customizationLevel), and the description compensates with nothing. The enum values are only loosely self-explanatory; the description does not explain what 'managed' vs 'full' ownership means or how the two axes interact to select a UI mode.

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 and tool name ('MediaSFU Vue :: ui.mode.recommend') plus a parenthetical alias '(ui-advisor)'. It never states in plain language what the tool does or what it recommends. The alias hints at advisory behavior but the agent must guess the resource and output.

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 alternatives such as vue::ui.overrides.guide or vue::sdk.recommend, which sit alongside it in the sibling list. The 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.