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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false; the description's 'known to this service' is consistent with that closed-world claim but adds little. It does add one genuinely useful behavioral fact not in the annotations: each zone entry includes 'the rules for each', indicating a rules payload rather than bare identifiers. No guidance on result size, pagination, or freshness.

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?

One clean sentence, front-loaded with the verb and resource, with zero filler. It is efficient but arguably under-specified for a listing endpoint rather than optimally structured.

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?

Annotations cover the safety profile and no output schema exists, so the description need not explain returns. But with a 1-param free-form query object and four closely named clean-air/vehicle siblings, the definition leaves the agent without the filtering semantics or the routing rule needed to call it confidently.

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 baseline is 3; the single 'query' parameter is documented in the schema as 'Optional query parameters'. The description adds nothing about it, and the schema itself is a free-form bag accepting string/number/boolean values, so the agent learns neither accepted keys nor filtering syntax from either source.

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?

States a specific verb (List) and resource (UK clean air zones) plus the payload detail 'the rules for each', so the agent knows exactly what comes back. However, it does nothing to distinguish this from the sibling clean_air_zones (or clean_air_catalogue / clean_air_check), so an agent choosing between near-identical names gets no help from the text.

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 when-to-use, when-not-to-use, or alternative routing. The phrase 'known to this service' faintly implies this is a local catalogue rather than a live lookup, but the agent is never told to prefer clean_air_zones, clean_air_check, or vehicle_check_clean_air in any circumstance.

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