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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing: not whether the call is read-only, whether it mutates config, what it returns, or what inputs drive the recommendation. The label 'ui-advisor' is not behavioral disclosure.

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 very short, but this is under-specification rather than conciseness. Nothing is front-loaded because there is no substantive content to front-load.

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 output schema, no annotations, and two undocumented enum parameters, the description should explain inputs, behavior, and output expectations. It supplies none of this, leaving the agent unable to invoke 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?

Two parameters exist (ownershipLevel, customizationLevel) with 0% schema description coverage and no explanation in the description. The enum values are partly self-describing (managed/partial/full, low/medium/high), but the description adds no meaning about how these levels 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 description only restates the tool name plus a parenthetical tag '(ui-advisor)'. It hints that the tool advises on UI mode selection, but gives no verb-resource statement of what it actually does and offers nothing to distinguish it from siblings like reactjs::ui.overrides.guide or reactjs::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 when-to-use guidance, no prerequisites, and no mention of alternative tools. An agent cannot tell when this recommender should be invoked versus ui.overrides.guide or the broader sdk.recommend sibling.

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