air_quality_dubai

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and repeat-call profile is covered. The description's one genuine addition beyond structured data is 'real-time' (data freshness), which is useful but thin — no mention of update cadence, caching, or data source.

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?

Two short sentences, front-loaded with the purpose. However, the second sentence enumerates return fields (AQI, pollutants, dominant pollutant) that the existing output schema already carries, which is mild redundancy rather than waste.

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 an output schema, rich annotations, and full schema coverage on the one parameter, the description only needs to supply purpose and freshness — both present. The residual gap is routing among the three air-quality siblings, which the description does not address.

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% and the single station parameter already documents its default and valid IDs, so the baseline is 3. The description only restates 'for a Dubai station' and adds no syntax, default, or selection guidance 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?

States a specific verb and resource with scope: 'Get real-time air quality for a Dubai station.' That is clearly distinct from air_quality_by_coords, but the description never names or contrasts with its two closest siblings (air_quality_by_coords, air_quality_dubai_stations), so differentiation is left to the agent's inference from names.

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?

'for a Dubai station' implies station-keyed lookup as opposed to the coordinate-based sibling, which is implied routing rather than stated guidance. There is no explicit when-to-use, no note that air_quality_dubai_stations may be needed to discover valid station IDs, and no exclusions.

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