Search one-way flights with all filters.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date YYYY-MM-DD | |
| stops | No | 0=any, 1=nonstop, 2=1stop, 3=2stops | |
| adults | No | Passengers (default: 1) | |
| arrival | No | Arrival IATA code | |
| country | No | Country (default: us) | |
| currency | No | Currency (default: USD) | |
| departure | No | Departure IATA code | |
| travel_class | No | 1=Economy, 2=Premium, 3=Business, 4=First |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Search one-way flights with all filters' and gives no information about return format, rate limits, authentication requirements, or any side effects. This is a significant gap for a tool with no annotation support.
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 concise sentence that front-loads the core purpose. It is not verbose or wasteful, though it lacks structure and additional context. For a tool with 8 parameters, one sentence is appropriately brief but could benefit from more organization.
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 tool has 8 parameters, no output schema, and no annotations. The description only states a general search capability without explaining what 'all filters' means, how results are returned, or any defaults. This is incomplete for a complex search tool.
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?
The schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, but it does not need to compensate given the high schema coverage.
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 searches for one-way flights, with a specific verb and resource. However, it does not differentiate from siblings like 'flight_search' or 'cheapest_flights', so it loses some points on sibling distinction.
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 guidance is provided on when to use this tool versus alternatives such as multi_city or price_calendar. The description implies one-way searches but does not explicitly state exclusions or scenarios where another tool would be preferred.
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.