tool_search_flights

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

No annotations provided, but description fully covers behavioral traits: 'Read-only. No auth required. No rate limits enforced. Data freshness: scraped live at call time; prices may shift minute-to-minute. Returns a list of flight options each with price, stops, duration, airline, and booking deeplink.'

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?

Well-structured: purpose sentence, behavioral summary, usage guidelines, then parameter list. Every sentence is informative and earns its place.

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 8 parameters, no output schema, no annotations, and many sibling tools, the description is fully complete. It explains parameters, return structure, usage context, and behavioral traits without gaps.

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 0%, but the description lists all 8 parameters with meaningful details: IATA code formats, date format, omission for one-way, adult range, max_results range, currency examples, and nonstop_only as boolean. Adds significant value beyond 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 'Search live flight prices between two airports using Google Flights data.' It specifies the verb (search), resource (flight prices), and distinguishes from sibling tools.

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?

Explicitly says 'Use this when the user wants to compare specific flight options for a known origin-destination pair.' It also lists four sibling tools with specific use cases (tool_fare_calendar, tool_find_cheapest_month, etc.).

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