Search Google Flights

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

Describes basic behavior (search, return options) and limitations (no policy/booking). With no annotations, it should disclose more (e.g., read-only, API dependencies).

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 purpose, no unnecessary words. Efficient and clear.

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?

Mentions return structure (airline, times, stops, price) since no output schema. Lacks pagination or error details, but adequate for a 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?

Schema has 67% parameter descriptions. The description adds no extra parameter guidance; it only mentions output fields. Baseline score applies.

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?

Clearly states it searches Google Flights and returns structured flight options. Distinct from sibling tools like check_policy and start_booking.

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 it does not check policy or book anything, clarifying its scope. However, it doesn't explicitly direct to find_compliant_flights for policy-compliant searches.

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