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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-structured context: the upstream source (Defra UK-AIR), that the figure is a measured hourly reading rather than a forecast, that the monitor must be 'working', and a 1-credit cost. It stops short of saying what happens when no monitor falls within max_km.

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 key output and its units are front-loaded in the first clause, and source, non-forecast caveat and cost are tacked on compactly. The middle sentence about summer smog and countryside-versus-city levels is interpretive padding, but it is short and helps an agent relay the value sensibly.

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 necessary work by spelling out the returned fields (reading, 8-hour mean, DAQI band, health advice) and the data provenance. The main gap is the no-nearby-monitor case and data staleness, which an agent cannot infer.

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% and all three parameters carry their own descriptions, so the baseline is 3. The description reinforces the 'nearest' semantics behind lat/lon and max_km but adds no range, unit or fallback detail beyond what the schema already states.

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 opens with a specific verb and resource: 'Latest hourly ground-level ozone (O3) reading in ug/m3 at the nearest working Defra AURN monitor', and enumerates the extra returns (8-hour mean, DAQI band, health advice). An agent can distinguish it from no2_level_near/pm10_level_near/pm25_level_near purely from the named pollutant and units, without opening the schema.

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?

It gives audience framing ('suits runners and people with lung conditions in heatwaves') and an explicit exclusion ('Not a forecast'), which implies when it is appropriate. However, it never routes the agent between this and the close siblings air_quality_index_near, no2_level_near, pm10_level_near or pm25_level_near, so the choice among pollutant tools is left to inference.

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