Air quality and the cleanest window to be outside

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

With no annotations, the description carries full responsibility. It transparently discloses the data source (Copernicus CAMS), the use of US AQI standards worldwide, the EPA-based verdict, and the forecast-window behavior. It does not mention rate limits or response structure, but the key limitations are well covered.

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 description is two sentences, front-loading the core outputs and ending with a necessary caveat about data quality. No filler words; every clause contributes meaningful information.

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?

Given there is no output schema, the description explains the main result categories (AQI, pollutants, EPA verdict, clean window) and the window-finding behavior. It could specify how the window is computed or whether AQI is instantaneous versus averaged, but the essential functionality is clearly conveyed.

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%, so the baseline is 3. The description reinforces the roles of 'hours' and 'duration' in finding the cleanest window, but the schema already provides clear descriptions for each parameter, so the description adds limited additional semantic value.

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 clearly enumerates specific deliverables: current US AQI, pollutant breakdown, EPA-based exercise safety verdict, and the cleanest contiguous window. It distinguishes itself from the unrelated sibling tools by focusing on air quality and outdoor activity planning.

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?

The description implies the main use case (assessing air quality for outdoor exercise) and offers a 'when not' by noting the data is modelled and not from a sensor at the exact spot, which cautions against use when precise local measurements are required. However, it does not explicitly name alternative tools or provide formal 'use this when' guidance.

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