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 the tool is read-only, whether it inspects project state, what inputs it expects, or what it returns. The only content is aliases, which conveys no behavior.

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 brevity here is under-specification rather than conciseness — the space given to alias strings would be better spent explaining the tool. It is at least not padded with noise.

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 two-parameter advisory tool with no annotations, no output schema, and no parameter documentation, the definition supplies none of the information an agent would need to invoke it correctly. The name-restatement plus aliases cannot carry the load.

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?

Both parameters ('ownershipLevel' with managed/partial/full and 'customizationLevel' with low/medium/high) have 0% schema description coverage, and the description adds nothing about their meaning or how they influence the recommendation. With two undocumented enum parameters, the description fully fails to compensate.

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 ('MediaSFU Unity :: ui.mode.recommend') plus a parenthetical '(ui-advisor)' and a list of aliases. It never states what is actually recommended — a UI mode, a rendering approach, a layout strategy — or what the recommendation is based on, so the agent must guess from the name alone.

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 is mentioned. The sibling 'unity::ui.overrides.guide' is clearly adjacent and the description offers no way to choose between them.

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