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 states 'No identifiers are retained', which is a privacy note, but it does not disclose whether the operation is read-only, whether it makes network calls, or what side effects occur. The parameter hints like 'discarded' and 'no disk access' are in the schema, not the main description.

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 only two sentences, which is under-specified for a tool with 9 parameters. The first sentence is vague and the second offers a single detail. It is not conciseness but inadequacy – it does not earn its place.

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?

Given the complexity of 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the classification result looks like, how the inputs are combined, or what an agent should expect as output.

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% – every parameter has a clear description (e.g., 'Git ref name; discarded after the shape check'). The tool description adds no additional semantic value, so the baseline 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 says 'Show how this request is classified' but does not define what 'request' means, what classification scheme is used, or how this differs from siblings like domain-shape, validate-json, or normalize-url. It is vague and lacks a specific verb-resource pair.

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 on when to use this tool versus any of the 27 sibling tools. No context, prerequisites, or exclusions are mentioned, leaving an agent without a basis for selection.

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