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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that results include charges and rules, but says nothing about pagination, filtering behavior, or whether the free-form query is forwarded to the upstream service.

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 front-loaded sentence that communicates source, resource, and return content with zero filler. Nothing to trim.

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?

For a tool returning charges and rules with no output schema and an arbitrary passthrough query object, the description should at least sketch what the zones record contains or what query keys exist. It leaves both the input contract and the return shape effectively unexplained.

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 reported as 100%, but the single parameter is an unconstrained free-form object accepting any string/number/boolean key, and the description does not name any supported query keys or formats. Baseline 3 applies since the schema nominally documents the parameter, but the description adds no real meaning.

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 clear verb (List) and resource (UK clean air zones) plus the value-add content (charges and rules). It does not differentiate from close siblings such as clean_air_catalogue, clean_air_check, or vehicle_zones, so an agent cannot tell from the description alone which list-like tool to pick.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives despite several plausible competing list/check tools in the sibling set. The agent must infer usage from the name alone.

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