compare_airports

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral constraint (max 6 combinations) that the schema does not enforce via maxItems, but it says nothing about result ordering, per-combination failures, or cost/latency of fanning out across many combos.

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?

A single front-loaded sentence with zero filler; the scope limit is stated inline where it matters. Nothing could be trimmed without losing meaning.

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?

An output schema exists, so return values need no explanation, but for an 8-parameter, low-coverage tool the description is thin: no mention of round-trip vs one-way handling (return_date), cabin/currency effects, or how ties among combos are resolved. Adequate to call the tool, not to call it confidently.

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 only 38% (3 of 8 params): cabin, adults, currency, max_stops, and return_date are undocumented in both schema and description. The description only gestures at origins/destinations and fares, so it does not compensate for the coverage gap on an 8-parameter tool.

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?

States a specific verb (Compare) and resource (cheapest fare across origin/destination airport combinations), plus a precise scope limit of max 6. It does not name or contrast against the siblings find_cheapest_dates or search_flights, so the agent must infer the boundary between this batch-comparison tool and a single search.

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 when-to-use, when-not-to-use, or alternative-tool guidance is given. The agent can loosely infer this is for multi-airport comparison, but nothing tells it how this differs from search_flights or find_cheapest_dates, and the max-6 budget is stated without explaining what happens if exceeded.

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