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

With no annotations, the description carries the behavioral disclosure burden. It offers a useful privacy guarantee ('No identifiers are retained') and implies a read-only action with 'Show', but it does not describe the classification output, external calls, or error behavior. It is a thin but not entirely empty disclosure.

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 two sentences are tightly written and front-load the primary action before the privacy guarantee. No words are wasted, though the brevity does contribute to the overall under-specification.

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?

This tool has nine optional parameters, no output schema, and no annotations, so the description needs to explain the classification behavior at a high level. It only gives a one-line purpose and a privacy note, leaving an agent unable to predict the result format or how to select among the many input fields.

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 each of the nine parameters already has a per-field description in the schema, so the baseline is 3. The tool description adds no extra meaning about how the parameters map to the classification, but it does not need to repeat schema details.

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 provides an action ('Show') and a resource ('this request'), but it never explains what classification means, what categories exist, or what 'compatibility' refers to. It also does not differentiate this tool from sibling shape/validator tools such as domain-shape or validate-json.

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 about when to use this tool, when not to use it, or which alternative would be preferable. The privacy note 'No identifiers are retained' implies a tradeoff, but it does not tell an agent why to choose this over normalize-url, validate-json, or other shape checkers.

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