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

The only behavioral note is 'No identifiers are retained,' which addresses privacy but does not disclose what the tool does with the input, what it returns, or whether it has side effects. Without annotations, the description should provide more transparency, but it is insufficient.

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 and to the point, with no unnecessary words. However, its brevity comes at the expense of necessary detail, making it under-specified rather than effectively concise.

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 explanation of how the tool works, the description is severely incomplete. It does not cover what the tool does with these diverse parameters (URL, city, JSON, path, etc.) or what a 'compatibility' check involves, leaving major gaps for the agent.

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?

Each parameter has a brief schema description, but they are generic and do not clarify the tool's purpose. For example, 'ref' is described as 'Git ref name; discarded after the shape check,' but what is a 'shape check'? The descriptions do not explain how the parameters relate to the tool's functionality, leaving the agent uncertain about how to fill them.

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 what kind of classification is performed, what 'compatibility' means, or what output is produced. The verb 'show' is weak and the resource is undefined, making it difficult to understand the tool's purpose.

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 indication of when to use this tool compared to its siblings (e.g., normalize-url, validate-json, timezone). The description does not differentiate it from alternatives or explain in which scenarios it is appropriate.

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