Air compare locations

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

No annotations exist. The description only says 'compare current readings,' which is a read operation, but it does not explain behavior like rate limits, error handling, or what 'default' means when the schema requires locationIds. This contradicts the required flag, adding confusion.

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 sentence with the verb 'compare' front-loaded. It is concise but could be more structured by separating the default clarification from the main action.

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?

For a simple tool with one required parameter and no output schema, the description is moderately complete. It lacks details on the output format, behavior on invalid IDs, and the nature of the comparison (e.g., table vs. list).

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 description adds minimal value. It mentions a default that conflicts with the required constraint in the schema, potentially misleading the agent. The schema already explains the parameter adequately.

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 tool compares current readings across multiple location IDs. It distinguishes from siblings like 'air_current_reading' (single location) and 'air_trend' (time series), making its purpose specific and unambiguous.

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 explicit guidance on when to use this tool versus alternatives. It implies comparison across locations but does not mention cases where other tools like 'air_aqi_check' or 'air_search_public_sensors' would be more appropriate.

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