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

With no annotations provided, the description carries the full behavioral burden, but it only says 'No identifiers are retained.' It does not disclose whether the tool is read-only, whether it accesses any external resources, what side effects it may have, or how the classification result is produced. The privacy guarantee is useful but does not make up for the missing operational detail.

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 deliberately short—the purpose statement comes first, and the privacy guarantee is a useful second sentence. There is no repetition and no padding. The brevity is a trade-off against completeness rather than a conciseness flaw.

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 required params, no output schema, and no annotations, yet the description provides no information about valid parameter combinations, what the classified output is, or how the result should be interpreted. An agent cannot reliably decide which fields count to provide or what to do with the return value.

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?

All 9 parameters are already documented with individual descriptions in the schema, and schema coverage is 100%, so the baseline of 3 applies. The tool description itself adds no per-parameter meaning beyond the schema, and it does not clarify how the different optional fields (ref, url, query, path, etc.) influence the classification outcome.

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 an action verb ('Show') and an object ('how this request is classified'), but it never defines what 'request' refers to, what classification categories exist, or what the output will look like. It is distinguishable from the shape-checking siblings only by being more general, yet the actual purpose remains ambiguous.

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 alternative, no mention of valid input conditions, and no reference to the many similar check/ok/shape siblings like normalize-url, validate-json, or domain-shape. The only additional sentence is a privacy statement, not usage context.

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