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 output is static documentation or generated code, not whether it can modify project files, not what role 'mode' plays. 'Aliases: unity, unity-sdk, csharp-unity' is metadata, not 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?

The text is short, but it is short because it is under-specified rather than efficient. Every token is spent restating the name and listing aliases, which is boilerplate an agent already has from the tool identifier.

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 annotations, no output schema, and only 50% parameter coverage, the description must explain scope, output, and selection criteria. It explains none of these, leaving the agent unable to judge whether calling this tool is even appropriate.

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 50%: 'mode' has a one-line description while 'focus' has only an enum of six values with no explanation of their meaning. The description adds no parameter context at all, so it fails to compensate for the unlabeled enum values (branding, layout, cards, controls, headless-shell, native-bridge).

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 and its namespace, plus an alias list ('MediaSFU Unity :: ui.overrides.guide (ui-overrides)'). It never states a verb or what the tool actually produces (docs? generated override snippets? configuration?). An agent learns only the platform and topic, not the action, and nothing distinguishes it from siblings like unity::ui.mode.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, when-not-to-use, or alternative-tool guidance. The closest sibling, unity::ui.mode.recommend, is arguably a prerequisite or companion, but the description gives no hint of ordering or selection criteria. Usage must be entirely guessed from the name.

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