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

With no annotations, the description carries the full burden of disclosing behavior. It does state the operation is non-retaining and seems read-only ('Show...', 'No identifiers are retained'), but it does not explain whether the classification is local, what side effects exist, or what the response contains. This is minimal disclosure for an unannotated tool.

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 short sentences with no filler, and the operation is stated before the privacy caveat. The structure is clean and scannable; the brevity is a style strength even though the content is somewhat 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?

This tool has nine parameters, no output schema, and no annotations, yet the description does not explain what classification values are returned, how inputs are combined, or how to interpret the result. The per-parameter schema descriptions help, but the core behavior and output format are missing, leaving an agent with insufficient context to invoke it correctly.

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 schema already documents each parameter thoroughly (e.g., 'Git ref name; discarded after the shape check'). The description adds no per-parameter meaning, which earns the baseline 3; it neither improves nor harms parameter understanding.

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 says the tool will 'Show how this request is classified', which conveys an action and a subject, but it never defines what 'classified' means or what kind of classification is produced. The tool name 'compatibility' hints at the domain, but the description alone does not distinguish it from the many sibling shape and classification tools.

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 no statement about when to use this tool versus a sibling, no conditions, and no alternatives mentioned. The privacy note ('No identifiers are retained') is the only implicit hint, but it does not tell an agent when to choose compatibility over, say, domain-shape or validate-json.

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