get_airport_info

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

No annotations exist, so description carries full burden. It reveals it's read-only (implicitly), requires an API key, and has a 1,000 calls/month limit. However, it does not discuss error handling, idempotency, or exact return format beyond listing fields.

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 succinct: two sentences plus a bulleted argument list. Every sentence provides value, and the purpose is front-loaded. No fluff or repetition.

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 partially covers return values but lacks details on structure or error behavior. It also omits usage constraints (e.g., providing at least one param) and does not differentiate from siblings despite sibling list existing.

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 0%, so description must add meaning. It lists params with examples (e.g., IATA 'JFK') and indicates they are search filters. However, it does not explain mutual exclusivity or whether multiple can be combined, leaving ambiguity.

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 it retrieves airport details (Flughafen-Details) and specifies search by IATA, ICAO, or country code. It lists return data (name, location, timezone) and distinguishes from siblings like arrivals/departures/weather.

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 mentions API key requirement and call limit, but does not explicitly state when to use this tool versus siblings or how to combine parameters. It implies one search criterion but does not clarify if multiple are allowed or if at least one is required.

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