search_flights

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

With no annotations provided, the description fully covers behavioral aspects by stating it returns 'matching aircraft with estimated flight times and cost ranges,' indicating a read-only search operation. No contradictions exist.

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 extremely concise with two sentences, front-loading the action and purpose. Every sentence provides value with 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 the tool's simplicity, the description adequately covers purpose, usage, and output. No output schema exists, but the description mentions 'estimated flight times and cost ranges,' which is sufficient for agent invocation.

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?

All 4 parameters have 100% schema description coverage, so the baseline is 3. The description adds no additional meaning beyond the schema, as it only reinforces the city pair concept already defined in the parameters.

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 uses a specific verb ('Search') and resource ('available private jet aircraft for a city pair'), clearly stating what the tool does. It distinguishes from sibling tools like get_destinations and get_fleet by focusing on route-based search and returning estimated flight times and cost ranges.

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?

Explicit guidance is provided: 'Use this when a user mentions a route (e.g., 'New York to London').' This clearly indicates the triggering condition, though it does not mention when not to use, which is acceptable given the straightforward context.

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