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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description adds trip-type scope, but does not disclose auth needs, rate limits, price freshness, or whether results are live offers versus cached data.

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 compact sentences with the primary purpose front-loaded. Every clause either states scope or routes the agent to the correct sibling, with no redundant restatement of the tool name.

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 an output schema present, the description does not need to explain return values, and annotations already cover read-only/open-world behavior. Given the tool's complexity, the description still covers purpose, scope, location-input workflow, and sibling differentiation sufficiently for correct selection and invocation.

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 coverage is 100%, so the baseline is 3. The description adds meaningful workflow context for the required from/to parameters by directing the agent to booking_flights_autocomplete, which is not stated in the schema itself, though it does not add detail for the remaining nine parameters.

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 (Search), resource (Booking.com flight offers), and scope (one-way or round-trip, between two locations). It also distinguishes itself from sibling hotel tools by naming booking_search and booking_hotel_detail as hotel rather than flight 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 names booking_flights_autocomplete as the tool to resolve location inputs, which is the key prerequisite for the required from/to parameters. It also clarifies that booking_search and booking_hotel_detail cover hotels rather than flights, giving clear when-not-to-use guidance.

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