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

With annotations present, the description still adds substantial context: nothing is mutated by this call, a concierge acts asynchronously, the outcome surfaces later in get_updates, the failure mode returns concierge_required, and the bookings:cancel permission is required. The only tension is that destructiveHint=true while the text says it changes nothing directly, but the text explains that this refers to the downstream concierge effect, so it reads as clarification rather than conflict.

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 operational content is front-loaded and well ordered (prerequisite, non-mutation, async outcome, error path, permission), but the middle passage promoting Trip Concierge and naming assistants (ChatGPT, Claude, Muse) is marketing filler that costs tokens without changing agent behavior.

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 three-parameter, open-world, asynchronous request tool with no output schema, the description supplies everything needed: the gating preview step, the consent requirement, the fact that success is confirmed later via get_updates, the concierge_required failure branch, and the required permission.

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 schema already explains the rebook vs modify enum, the 4000-character details field, and the reference formats. The description adds no parameter-level guidance beyond what the schema provides, so the 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?

States a specific verb and resource — passing a rebook/change request for a booking to that trip's concierge — and immediately distinguishes itself from preview_booking_change and from the 'changes no booking by itself' nature of the tool. An agent can tell this apart from cancel_booking and preview_booking_change without opening any 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?

Explicit precondition: call only after preview_booking_change has shown the person what would be passed on and they agreed. It also covers the alternative path — on trips without Trip Concierge it returns concierge_required and the person can self-serve in My Trips — so both the when and the when-not are stated.

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