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

With no annotations, the description must carry the full behavioral burden. It only offers a privacy guarantee ('No identifiers are retained') but does not disclose whether the tool performs any external calls, mutates state, or what side effects exist. The per-parameter notes about discarding data are in the schema, not the description, and are not summarized.

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 extremely short (two sentences) and could be concise, but it is under-specified. It lacks critical information about purpose and usage, so its brevity is a deficit rather than a strength. The front-loaded 'Show how this request is classified' is not informative.

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 is a 9-parameter tool with no output schema, no annotations, and a vague one-line description. The agent is left without any idea of what the tool returns, when to invoke it, or how to interpret its results. The description is far from sufficient for correct invocation.

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 the schema fully documents each of the 9 optional parameters. The tool description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 applies. It does not explain how the parameters relate to the classification.

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 purpose but it is vague: 'Show how this request is classified' does not specify what classification means, what resource is acted on, or what output is produced. It does not differentiate from sibling shape-checking tools like domain-shape or validate-json, which each have clear, specific purposes.

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 guidance is given on when to use this tool versus the many siblings. There is no mention of conditions, alternatives, or exclusions. An agent would have no idea when to prefer 'compatibility' over a specific shape-checker like github-repo-shape.

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