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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about behavior: no indication of whether it is read-only, what it recommends from, or how the two inputs shape the recommendation.

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 the brevity is under-specification rather than conciseness; the single string carries no useful front-loaded information beyond the tool name.

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 recommendation tool with two enum inputs, no annotations, and no output schema, the definition omits everything an agent would need: selection criteria, input meaning, and expected output.

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 coverage is 0%, and both enums (ownershipLevel, customizationLevel) are undocumented in both schema and description. The description adds no meaning about what these levels control or how they affect 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 text is essentially a restatement of the tool name ('ui.mode.recommend') plus a parenthetical alias ('ui-advisor'). It implies a recommendation of a UI mode but gives no verb-based statement of what it actually does, no scope, and no distinction from siblings like ui.overrides.guide or sdk.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 guidance on when to call this tool, what inputs trigger it, or how it relates to the many sibling advisors. An agent has nothing to route on.

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