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

Annotations already declare a safe read-only, closed-world operation, so the description's job is to disclose what the review does — and it does: it lists per-type checks, universal checks, a high/medium/low rating scheme, and the important limitation 'Pattern checks on single strings in English'. It stops short of describing the output shape, but the scope and limits are well disclosed.

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?

Purpose and input contract are front-loaded, followed by the check lists. It is dense and the long parenthetical enumerations read as run-on, but nearly every clause carries actionable instruction — the slight sprawl keeps it from a 5.

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 single-parameter, no-output-schema tool, this covers input format, type taxonomy, check scope, severity scale, and a language limitation. The main omission is any hint of the response structure beyond the severity ratings.

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 coverage is 100% and the single parameter is already documented, so the baseline is 3. The description adds real value by enumerating the complete set of valid type prefixes (button, link, label, tooltip, empty, confirmation, placeholder, heading), which the schema only hints at with one example.

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?

States a specific verb and resource ('Review interface strings') and immediately defines the input format, so the agent knows exactly what it consumes. It does not explicitly differentiate itself from near neighbors like review_ui_copy, plain_language_check, or error_message_check, which keeps it at 4 rather than 5.

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?

The description gives strong 'how' guidance (one item per line with a type prefix) but no explicit 'when' guidance — nothing says when to reach for this versus review_ui_copy or the narrower error_message_check/notification_copy_check tools. Usage is implied by the enumerated string types rather than stated.

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