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

No annotations are provided, so the description carries full behavioral disclosure burden. The statement 'No identifiers are retained' adds a useful privacy/retention trait, but it omits other behavioral details such as whether network calls are made, what side effects exist, or how the classification result is returned.

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 short and to the point, with no wasted words. Its two sentences front-load the core action and then add the privacy statement, though the first sentence is somewhat vague.

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?

With no output schema and no explanation of return values or classification semantics, the description is incomplete for a tool that classifies requests. The purpose is ambiguous and there is no guidance on what an agent should expect after calling it.

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?

The input schema already provides descriptions for all seven parameters, including discard behavior for ref, city, and json. The tool description adds no parameter-level meaning beyond that, so the schema is doing the heavy lifting.

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 uses a verb 'Show' and a resource 'request', but 'how this request is classified' is vague: it never defines what classification means or what output is produced. It also does not differentiate the tool from sibling shape-check or hint tools such as domain-shape or github-repo-shape.

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 about when to use this tool versus alternatives, no explicit conditions or exclusions, and no mention of which sibling tools overlap. The privacy note is implicit context but does not tell an agent how to select or invoke the tool.

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