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

The description mentions that no identifiers are retained, implying a privacy-safe behavior, but does not state whether the tool has any side effects, modifies data, or returns sensitive information. Without annotations, the description leaves uncertainty about the tool's full behavioral impact.

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 very brief, consisting of two short sentences. It front-loads the main purpose and then adds a privacy note, making it concise and well-structured.

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?

The description lacks any information about the output format or content, making it impossible to know what the tool returns. It also does not clarify the tool's niche among the many sibling tools, such as whether it overlaps with 'normalize-url' or 'fetch-status'.

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 schema descriptions for all 9 parameters are present and clear, covering the meaning of each field. The tool description itself adds no further explanation of how parameters interact or affect the classification, so it relies entirely on the schema.

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 'Show how this request is classified' but does not specify what classifications exist or what exactly is being classified. It is vague about the tool's core function and lacks a specific verb like 'get' or 'check' that would clarify the action.

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 provides no guidance on when to use this tool versus alternatives. The only additional note is about identifier retention, which is a privacy concern rather than usage direction.

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