Google Flights Remote MCP Server

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context beyond that: it details the return payload (price, duration, stops, legs, aircraft, CO2 emissions) and the token flow for round-trip/booking follow-ups, though it omits rate limits, auth, and pagination.

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?

Front-loaded with a clear purpose line followed by a dense but informative summary of inputs and outputs. The mega-sentence is long and the trailing use-case list is somewhat filler, but nothing is materially wasted.

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 31-parameter tool with no output schema, the description usefully compensates by describing the return structure and the departureToken/bookingToken follow-up flow. Required parameters and their formats are covered by the schema; only operational details like errors and rate limits are absent.

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 schema already documents all 31 parameters with enums and examples. The description's summary of the parameter space (passenger mix, class, bags, max price, sort, stops, airline filters, time windows, layover, deep search) adds framing but no syntax or format detail 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?

States a specific verb and resource ('Searches Google Flights for one-way, round-trip, or multi-city itineraries') and enumerates the concrete filtering scope, making it unmistakably distinct from the sibling deals and hotels tools. An agent can identify the tool's function without opening the schema.

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 closing sentence lists intended audiences and scenarios ('travel-planning agents, fare monitoring, corporate travel dashboards, emission-aware trip optimization'), which implies usage but gives no conditions for choosing this tool over getGoogleFlightsDeals or getGoogleHotels. No explicit when-not or alternative guidance is provided.

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