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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the Defra UK-AIR source, hourly freshness ('latest hourly'), a 1-credit cost, and the important caveat that a single monitor can be several km away and not represent your street.

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?

Front-loads the return payload (value, units, band, advice) before the interpretive and audience framing. The middle sentence about diesel pollution and cyclists is longer than strictly necessary but earns its place as usage guidance; nothing is redundant with the annotations.

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 no output schema, the description does the work of describing the return payload (reading in ug/m3, DAQI band 1-10 with Low to Very High, health advice) and adds a source and accuracy caveat. The main gap is edge-case behavior: it does not say what happens when no working monitor falls within max_km.

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%, including lat/lon bounds and the max_km default of 25 with a 100 km cap, so the schema carries the parameter burden. The description mentions a 'nearest working monitor' but does not explain the search radius behavior or how max_km trades distance against representativeness, adding little beyond the schema.

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?

Names a specific pollutant, metric and source: latest hourly NO2 in ug/m3 from the nearest working Defra AURN monitor, plus DAQI band and health advice. The pollutant is embedded in the tool name and restated with domain framing ('traffic and diesel pollution'), which cleanly separates it from the pm25_level_near / pm10_level_near / ozone_level_near siblings.

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?

Gives clear usage context by naming the exact question it answers ('how bad is the traffic pollution near me right now') and the audiences it suits (cyclists, school-run parents, people with asthma). It stops short of explicit alternatives or when-not-to-use rules, e.g. it never says to prefer air_quality_index_near for an overall index or pm25_level_near for particulates.

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