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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the call is read-only, whether it returns a recommended mode, what inputs it assumes, or whether it mutates project configuration. '(ui-advisor)' is a label, not a behavioral statement.

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 that brevity stems from under-specification rather than efficiency. The single fragment is a name-plus-alias with no front-loaded statement of what the tool actually returns or does.

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 undocumented enum parameters, no annotations, and no output schema, the description should explain the recommendation it produces and the axes that drive it. It supplies none of this, leaving the agent with effectively no basis for invoking 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 0% and the description says nothing about 'ownershipLevel' (managed/partial/full) or 'customizationLevel' (low/medium/high). While the enum values are somewhat self-descriptive, the description adds zero meaning about what these dimensions mean or how they influence the recommendation.

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 merely restates the tool name ('ui.mode.recommend') with a parenthetical tag '(ui-advisor)'. The word 'recommend' does imply an advisory verb, but the resource ('ui mode') is only conveyed by the dotted name itself, and the gloss 'ui-advisor' is a synonym rather than an explanation. It is close to tautology, though not wholly absent of signal.

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?

No when-to-use, when-not-to-use, or alternative routing is provided. A sibling 'ui.overrides.guide' exists and is never mentioned, so an agent cannot tell whether to call this advisor or the overrides guide from the description alone. The only weak signal is the advisory framing implied by 'recommend'.

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