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

With no annotations provided, the description fully carries the behavior disclosure burden. It does reveal one useful fact—'No identifiers are retained'—but it omits whether the operation is read-only, what 'classification' means, or any side effects. For an unannotated tool with four parameters, this is insufficient behavioral context.

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 avoids redundancy, with both sentences adding something. However, the brevity borders on under-specification: 'show how this request is classified' is a tagline rather than a complete operational description. It is concise but not fully 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?

For a tool with four optional parameters, no output schema, and no annotations, the description is too sparse for an agent to confidently decide when to invoke it. The schema explains the parameters but not the purpose or expected result. The privacy note is helpful but not enough to make the tool self-explanatory.

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 parameters are already self-documenting. The description adds no parameter-specific meaning, but it compensates slightly by noting that identifiers are not retained, which complements the 'json' parameter's 'discarded after the check' hint. This meets the baseline for high schema coverage.

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 verb ('show') and a resource ('this request'), but 'classified' is vague—it doesn't specify what classification system or categories are involved. It also doesn't distinguish the tool from siblings like 'citation' or 'domain-shape.' An agent would still need to infer the actual operation from the parameter names.

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?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention what input conditions warrant calling it. The only contextual hint is the privacy statement, which is a behavior note, not a usage guideline.

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