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

With no annotations, the description must disclose behavioral traits. It states 'live' data from OpenAQ but omits important details such as data freshness guarantees, potential rate limits, error handling for invalid coordinates, or whether the tool is purely read-only.

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 a single concise sentence that immediately conveys the tool's purpose. Every word contributes meaning, and there is no redundant or filler content.

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 no output schema, the description should at least hint at return structure. It mentions AQI and pollutant levels but does not describe the format (e.g., numeric values, units). For a simple retrieval tool, this is marginally acceptable but lacks full clarity.

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 0%, so the description should add value. It mentions 'latitude/longitude' but does not specify valid ranges, format (e.g., decimal degrees), or any constraints beyond what is obvious from parameter names and schema examples.

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 states the action ('retrieves'), the resource ('live localized air quality indices and pollutant levels'), and the input ('latitude/longitude using OpenAQ'). It effectively distinguishes from sibling tools by specifying the unique data type (AQI) and source.

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 guidance is provided on when to use this tool versus alternatives (e.g., other location-based tools like getPollenCount or getUvIndex). There is no mention of scenarios where it is or is not appropriate.

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