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,' a privacy guarantee, but does not disclose whether the tool performs reads, writes, network calls, or any side effects. The schema hints at 'discarded' data, but the description itself does not clarify the tool's runtime behavior or side effects.

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 short, but this is under-specification rather than effective conciseness. It contains only a vague purpose and a privacy note, omitting essential details about behavior and usage. The single sentence does not earn its place because it communicates almost nothing actionable.

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?

With 9 parameters, no output schema, and no annotations, the description is severely incomplete. It gives no information about expected return values, error conditions, or how the parameters interact. An agent cannot correctly invoke this tool based on the description alone; it is essentially a black box.

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 has 100% description coverage, so the baseline is 3, but the description adds nothing beyond the schema. The schema entries like 'Git ref name; discarded after the shape check' are themselves terse and do not explain how the parameter contributes to 'classification.' The description does not bridge the gap, leaving the role of each parameter in the tool's operation unexplained.

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 names no specific verb-object pair, no classification scheme, and no resource. It does not differentiate from siblings like domain-shape or url-ok, which are specific about what they check. The name 'compatibility' hints at a broader purpose, but the description leaves the actual function opaque.

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 guidance on when to use this tool versus any sibling. No mention of prerequisites, alternatives, or conditions that would make this the right choice. The description simply states an action without context, leaving an agent to guess when 'compatibility' is appropriate.

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