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

No annotations are provided, so the description must carry the full behavioral burden. It says nothing about whether the tool is read-only, how recommendations are produced, what side effects exist, or what the agent can expect from invoking it. The aliases add no 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 under-specified: it spends its only content on platform aliases rather than front-loading a usable purpose statement. It is concise but not meaningfully structured to help an agent select and invoke the tool.

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 and no annotations, the description needed to explain what a UI mode recommendation is and how the two enum parameters influence it. It does neither, leaving the definition functionally incomplete for an agent-facing tool.

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 never mentions 'ownershipLevel' or 'customizationLevel'. Even though both parameters have enums, their meaning and impact on the recommendation are left entirely to the schema and are not clarified by the description.

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 mostly restates the tool name, 'ui.mode.recommend', plus platform aliases. It identifies the platform (Apple/Swift/iOS) but does not state what the tool actually recommends or how it differs from siblings such as 'swift::ui.overrides.guide'. This is tautological rather than explanatory.

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 use this tool versus alternatives, nor any prerequisites or exclusions. The phrase '(ui-advisor)' hints at an advisory role but does not tell the agent when this specific tool is appropriate.

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