HasData Google Flights Deals

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: which fields always come back (dates, price, duration, stops, airline, booking link) versus which only appear for searches Google shaped itself (typical price, discount, destination photo), plus that the response includes derived destinations and date range. No permissions, rate limits, or pagination behavior are mentioned, keeping it short of 5 with annotations already carrying the safety story.

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 first sentence front-loads what the tool does, followed by the plain-language input examples, then the return payload, then filters, then use cases — a sensible order. It is dense and long-ish, but nearly every clause carries information (the conditional return fields and the derived destinations/date range are not stated anywhere else).

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 21 parameters and no output schema, the description is the only place describing what comes back, and it covers the return shape, the conditional fields, and the derived search information. Combined with a 100%-covered schema, an agent has enough to call it correctly; only the behavior of party-size repricing and the empty-result semantics of stops/airlines live exclusively in the schema, leaving minor room for improvement.

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% and the per-parameter descriptions are unusually rich (the maxDuration measurement caveat, the arrivalId requirement for every filter, the date-window spellings), so the schema does the heavy lifting. The description only groups the filters at a high level (trip type, cabin class, stops, dates, trip length, price and duration ceilings, airlines, party size), which maps onto the schema rather than adding meaning. Baseline 3 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?

The description states a specific verb and resource — turning a plain-language trip description into flight deals with Google choosing destinations and dates — which is far more than a restatement of the name. It implicitly separates this from the route-pinned sibling (getGoogleFlights), which requires arrivalId, but never names that alternative explicitly, so sibling differentiation is inferable rather than stated.

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?

"Use for inspiration-driven travel search, seasonal and event-based fare discovery, deal alerting, and travel-content generation" gives concrete when-to-use scenarios with examples of the query style (cherry blossom, beach escape, festival). There is no explicit when-not-to-use or named alternative for a user who already knows their exact destination and dates, which is the main remaining gap.

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