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

With no annotations provided, the description carries the full burden. It discloses that the tool is synchronous and typically takes 5-20 seconds, and that it provides live data. It does not mention rate limits, authentication requirements, or caching behavior, but the timing disclosure is valuable.

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 no unnecessary words. The first sentence captures purpose and output the second adds a critical behavioral note on timing. Highly efficient and front-loaded.

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?

For a tool with 5 parameters and no output schema, the description provides core purpose, data fields, timing, and route scope. It lacks details on result limits, error cases, or handling of no results, but overall it is reasonably complete.

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 the baseline is 3. The description adds minimal extra meaning beyond the schema—it confirms that the tool handles one route and one or more dates, but does not detail the effect of boolean parameters like 'nonstop' or 'oneway'.

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 it provides live Google Flights prices for one route across one or more dates. It lists specific data returned (airline, GBP price, duration, stops, times, booking link), distinguishing it from sibling tools like 'search_explore_anywhere' or 'search_stopover_itineraries'.

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 for querying flight prices on a specific route but does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it or provide context about sibling tools.

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