get_air_quality

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

No annotations provided. Description does not disclose behavioral traits such as rate limits, authentication requirements, error handling, data freshness, or behavior with invalid coordinates. Only states the API source without additional context.

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?

Well-structured with Args section and a practical example. Reasonably concise but the example adds value. Could be slightly more compact.

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?

Provides an example referencing output fields (us_aqi) and mentions the return type (AirQualityResponse). However, with no output schema and 5 parameters, it lacks full coverage of return structure and error scenarios, leaving gaps.

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?

Parameters are listed with basic descriptions (latitude/longitude ranges, timezone hints). However, 'hourly' lacks allowed variable examples, and 'domains' lists only three options but not a full enumeration. With 0% schema coverage, the description should provide more detail.

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?

Clearly states 'Get air quality data and forecasts from Open-Meteo Air Quality API.' specifying verb, resource, and source. Distinguishes from sibling tools like batch_get_air_quality (batch) and other data-type tools.

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?

Implies usage through example but provides no explicit guidance on when to use versus alternatives, no conditions or prerequisites, and no when-not-to-use advice.

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