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

There are no annotations, so the description carries the full behavioral disclosure burden. It does mention a privacy trait ('No identifiers are retained'), which adds some context, but it does not disclose whether the operation is read-only, what it computes, what it returns, or any side effects. This is thinner than the update_drive example that scored 2.

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 concise: two short sentences with no filler. The privacy statement earns some place, and the purpose statement is front-loaded. However, it is so underspecified that the compactness reflects omission rather than helpful organization, so it does not merit a 5.

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?

Given a 9-parameter tool with no annotations and no output schema, the description is far from complete. It gives no indication of what classification categories exist, what the output looks like, which parameters are meaningful for which use, or any example invocation. The agent cannot confidently invoke this tool correctly from the provided description alone.

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 baseline is 3 even without parameter information in the description. The description does not add any meaning beyond the schema, but the schema already documents all nine parameters, including discard behavior. The description's 'No identifiers are retained' loosely echoes the schema's 'discarded' notes without adding new semantic value.

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 and object: 'Show how this request is classified.' However, it is vague about what 'classified' means and does not identify what kind of classification result is produced. It does not distinguish this tool from the many shape-check siblings like domain-shape, validate-json, or file-path-ok.

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 usage guidance is provided. The description does not say when to use this tool over alternatives, what inputs are appropriate, or what conditions select this tool. The sibling list shows many possibly related checks, but the description gives no basis for choosing among them.

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