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 that identifiers are not retained, which is a privacy note, but it doesn't disclose whether the operation is read-only, whether it has side effects, or what happens to the input data. It doesn't address error handling, rate limits, or any other behavioral traits.

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 short (two sentences), which is concise, but it is under-specified. It lacks essential information, so it's not effectively concise – it's just brief. It does front-load the main statement, but that statement is 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?

For a tool with 9 parameters, no required parameters, no output schema, and no annotations, the description is grossly incomplete. It doesn't explain what the tool does with these parameters, what the classification means, or how an agent should interpret the output. This is inadequate for an agent to decide when and how to call 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 covers 100% of parameters with individual descriptions, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema provides – it doesn't clarify relationships, usage patterns, or any meaning that isn't already in 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 a verb ('show') and a resource ('classification'), but it is vague: it doesn't specify what kind of classification, what inputs trigger it, or what the output looks like. It does not differentiate from the many sibling tools that also analyze requests, such as domain-shape or fetch-status.

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 on when to use this tool versus alternatives. It doesn't mention any conditions, exclusions, or recommended scenarios, leaving the agent to guess.

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