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, and it discloses nothing: not whether this is read-only advice or a mutating setup step, whether it can be called repeatedly, or what output form it yields. A parenthetical label is not behavioral context.

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 that brevity comes from under-specification rather than economy. There is no front-loaded purpose sentence, just an identifier and a tag.

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?

A two-parameter recommendation tool with no annotations, no output schema, and no parameter documentation needs the description to supply purpose, inputs, and return behavior. None of that is present, leaving the definition effectively unusable for selection.

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). The description adds zero meaning — it doesn't explain what the enum levels represent or how they steer the recommendation, which is exactly the information the schema lacks.

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 essentially a restatement of the tool name plus a parenthetical label '(ui-advisor)'. It never states in plain language what the tool does — e.g. that it recommends a UI integration mode given ownership/customization constraints — nor how it differs from siblings like ui.overrides.guide or integration.plan.

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?

'ui-advisor' faintly implies this is an advisory/consultative tool, but there is no statement of when to call it, what inputs to have ready, or which alternative tool to pick instead. An agent cannot infer its place in the workflow.

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