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

The description explicitly states 'No identifiers are retained,' which is a useful behavioral and privacy guarantee, and 'Show' implies a non-mutating, informational operation. However, with no annotations provided, the description carries the full burden and does not disclose whether the tool makes network calls, what side effects occur, or how values are handled beyond the schema's own 'discarded' notes.

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 description is two short sentences with no filler. The primary action is front-loaded and the privacy note is relevant and economical.

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?

There is no output schema and the description does not explain what the classification response looks like, what classification buckets exist, or how the tool should be invoked meaningfully. The parameter schema is complete, but the tool's overall behavior and return value remain underspecified for a 9-parameter meta-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 100%, so every parameter is already documented with meaningful descriptions. The tool description itself adds no parameter-level semantics, so the baseline of 3 applies.

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 states a clear action ('Show how this request is classified'), but it does not define what classification means, what categories exist, or what 'this request' refers to. It is not a tautology, but it is vague and does not differentiate the tool from its many sibling validators and checkers.

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 no guidance about when to use compatibility versus any sibling tool. It does not mention alternatives, exclusions, or a concrete scenario in which the tool should be selected. With 26 siblings, this lack of usage direction is a significant gap.

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