Compare flight prices by airline for a route. Shows cheapest per airline, stops, duration.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date YYYY-MM-DD | |
| arrival | No | Arrival IATA code | |
| country | No | Country (default: us) | |
| currency | No | Currency (default: USD) | |
| departure | No | Departure IATA code | |
| return_date | No | Return date (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden. It uses read-oriented verbs ('Compare', 'Shows') and describes the output (cheapest per airline, stops, duration), but it does not disclose potential quirks, permissions, or confirm read-only behavior explicitly. This is adequate but not thorough.
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 two sentences, front-loaded with purpose, and every word earns its place. 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?
The description is minimal and does not explain that departure and arrival IATA codes are logically required despite schema marking all params optional. With no output schema or annotations, the description should clarify invocation expectations (e.g., need for date and route codes). It also does not differentiate usage from sibling tools, leaving gaps for an agent to invoke correctly.
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 100%, so all parameters are already documented. The description adds no extra parameter semantics beyond saying it shows 'cheapest per airline, stops, duration', which is not tied to specific parameters. Baseline 3 is appropriate.
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 flight prices by airline for a route, which distinguishes it from siblings like cheapest_flights and flight_search. The verb 'Compare' and specific resource 'flight prices by airline' make the purpose explicit.
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?
The description implies usage when one needs per-airline price comparisons, but it does not explicitly state when to use this tool over alternatives or mention exclusions. No alternative tools are named, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes (airport codes, multi-city, airline comparison), but flight_search and one_way_search overlap since flight_search already covers one-way trips. Descriptions help differentiate, but some confusion is possible.
All tools use consistent snake_case naming with a pattern of descriptive nouns or adjective-noun pairs (e.g., cheapest_flights, price_calendar). No mixing of styles.
8 tools cover the flight search domain well without being excessive. Each tool serves a specific purpose, and the count is appropriate for the server's scope.
The tool set covers key flight search needs: airport codes, round-trip/one-way/multi-city searches, price calendars, airline comparisons, and health check. No obvious gaps in the search/info domain.