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

No annotations are provided, so the description carries the full burden. It discloses that 'No identifiers are retained,' which is a privacy guarantee, but it does not state whether the operation is read-only, whether it has side effects, or any other behavioral traits (e.g., rate limits, required auth). The privacy note is a plus, but it is insufficient for a tool with zero annotation coverage.

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 two sentences, front-loaded with the primary purpose and followed by a privacy note. It is concise and avoids redundancy. However, the brevity borders on under-specification for a 9-parameter tool, though the conciseness dimension rewards efficiency over completeness.

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 tool has 9 optional parameters, no output schema, and no annotations. The description does not explain how the parameters are used in classification, what the output format is, or what the tool returns. An agent cannot infer correct usage or expected results from the description alone. This is a significant gap for a tool of this complexity.

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 provides 100% description coverage for all 9 parameters, each with a meaningful explanation (e.g., 'Git ref name; discarded after the shape check'). The description text itself adds no parameter-specific meaning beyond the schema. Per the rubric, baseline 3 is appropriate when schema coverage is high.

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 state a clear verb+resource (e.g., 'classify' vs 'show') or explain what classification means. It does not differentiate from siblings like validate-json or domain-shape, which also analyze inputs. The term 'request' is ambiguous.

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. It does not mention any sibling tools, use cases, or exclusion conditions. An agent has no basis for selecting this tool over others.

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