Search flights

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

No annotations are provided, so the description carries the burden. It adds a meaningful behavioral trait: 'Returns a unified flight list from the REST or website API', disclosing that results may come from different sources. However, it does not explain how the source is selected, potential limitations, or response behavior, which leaves gaps.

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 the core action, and every phrase adds value. No fluff or redundancy.

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 6 parameters, no annotations, and no output schema, the description provides a clear high-level purpose but misses details like return format, how the source enum affects behavior, and time-window semantics for hoursBack/hoursForward. It is adequate but not comprehensive.

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 67%, so baseline is 3. The description adds context for some parameters: 'arrivals or departures' clarifies direction, 'optionally filtered by flight number' reiterates flightNumber, and 'REST or website API' gives meaning to source. But it does not add information about hoursBack/hoursForward beyond what is in the schema.

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 'List flights for an AENA airport (arrivals or departures), optionally filtered by flight number', using a specific verb and resource. It distinguishes from sibling tools by explicitly covering flight listing, not individual flight details (get_flight) or airport lists (list_airports).

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 gives clear context for when to use the tool (listing flights for an AENA airport) but does not explicitly mention alternatives or when not to use it. It implies usage but lacks exclusions or comparison with get_flight or list_airports.

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