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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'No identifiers are retained,' which is a privacy guarantee but says nothing about side effects, network access, disk access, or whether the operation is read-only. The schema hints at 'discarded' for many parameters, but the description itself does not clarify the tool's overall behavior or any potential risks.

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 extremely brief (two short sentences), but this is under-specification rather than conciseness. It front-loads a vague purpose and adds a privacy note, but omits critical operational details. Every word is not earning its place because the content is insufficient for an agent to understand the tool's function.

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 9 optional parameters, no output schema, and no annotations, the description is grossly incomplete. It does not explain what classification means, what the output format is, how parameters interact, or what happens when multiple parameters are provided. An agent cannot call this tool correctly with the information given.

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%, with each of the 9 parameters individually documented (e.g., 'Git ref name; discarded after the shape check', 'JSON text to validate; discarded after the check'). The tool description adds nothing about parameters, but the schema already provides sufficient meaning. Per the rubric, a baseline of 3 is appropriate when schema coverage is high and the description doesn't detract.

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 'Show how this request is classified' is vague. It does not specify what resource is classified, what kind of classification is produced, or how it differs from the many sibling tools. The verb 'show' is weak and the object 'request' is ambiguous—it could mean the input payload or an HTTP request. It is not a tautology, but it lacks the specificity needed for an agent to know what this tool actually does.

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?

There is zero guidance on when to use this tool versus any of the 26 siblings. No context about selection criteria, prerequisites, or exclusions is provided. An agent has no way to know if this is the right tool for a given task, making the description unusable for routing decisions.

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