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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description is free to add what they cannot: the regional coverage asymmetry between US-centric wait/delay data and worldwide weather. It stops short of disclosing data freshness or what happens when an airport has no waits data, which would be the remaining useful traits.

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 sentences, front-loaded with what the agent gets, followed by the coverage caveat and the argument format. Every clause carries information and nothing is repeated from the schema or annotations.

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 present, return values need no explanation, and the description supplies purpose, coverage scope, and the required parameter's format. The only residual gaps are data freshness and behavior when US-specific wait data is unavailable, which are minor for a read-only aggregation call.

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 carries the burden for the single parameter and does so well, specifying that the airport argument accepts either IATA or ICAO codes with concrete examples (JFK/KJFK). This is exactly the guidance missing from the schema and prevents invalid-format calls.

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 names a specific verb-resource pairing (aggregated airport conditions) and enumerates exactly what is returned: delay programs, ground stops, security/immigration waits, weather, forecast, and recent traffic. This enumeration also implicitly separates it from narrower siblings such as airport_security_wait, since an agent can see this tool bundles their content.

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?

It gives real selection context by disclosing coverage limits: waits and delay programs are strongest for the US while weather is worldwide, which directly informs whether the tool is worth calling for a given airport. It does not name an alternative sibling (e.g., airport_security_wait for a single wait type) or state explicit exclusions, so it falls short of a 5.

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