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 note, but it does not reveal whether the tool reads data, performs mutations, requires auth, or what side effects it might have. The behavior of 'classification' is completely opaque.

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 with no filler. It front-loads the (vague) purpose and adds a useful privacy note. While the content is unhelpful, the structure is appropriately compact and the second sentence adds distinct information, so it earns a high score on conciseness.

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 accepts 9 diverse parameters (URL, city, JSON, path, zone, query, etc.) with no output schema and no annotations. The description provides zero guidance on how these parameters are used, what the classification output looks like, or what distinguishes this tool from the many specialized siblings. It is severely incomplete 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?

Schema coverage is 100%, so the baseline is 3. The description does not add any information about parameters beyond the schema, but that is acceptable given high coverage. No contradictions or misleading hints are present.

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—'classified' is undefined and doesn't specify a concrete action or resource. It does not distinguish the tool from siblings like browser-url-ok or geo-hint, which each have clear domain-specific purposes. The name 'compatibility' hints at a check, but the description fails to articulate that.

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 gives no indication of when to use this tool versus the many siblings. It provides no context, exclusions, or alternatives, leaving an agent without any guidance on selection criteria.

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