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

Beyond the annotations it discloses non-obvious behavior: cart status `completed` maps to dispatcher `PENDING_CONFIRMATION`, final `CONFIRMED` arrives via webhook, and `ERROR` returns 502 – all essential for interpreting a non-idempotent, open-world mutation. It also explains that responses expose partner sell in `price` and earn in `commission`/`clientCommission` while `providerPayment` is omitted, which is real behavioral context not present in annotations.

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 the core action and then the status/response semantics in compact sentences; every sentence carries information. The price/commission note is slightly tangential but still useful for interpreting the return value.

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 mutation tool with no output schema and 40% param coverage the description supplies the crucial missing pieces: async confirmation flow, error mapping, and response field semantics. It leaves the billing/traveler payloads and the prebook-prerequisite unsaid, but the core operational picture is complete.

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 only 40% and the description adds no parameter-level semantics for `billing`, `traveler`, or `customTags`; it only alludes to the payment step already documented by the schema's `transactionId` note. With the majority of parameters undocumented in both places, the description does not compensate for the coverage gap.

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 gives a specific two-step verb sequence (capture Stripe payment, confirm cart with experiences-api) and names the concrete resource (cart/prebook). It clearly implies the post-prebook booking step, though it never names a sibling like prebookExperienceTour to differentiate explicitly.

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?

Usage is implied: it consumes a prebookId from the prebook endpoint and completes the booking, and it hints that CONFIRMED arrives asynchronously via webhook. But there is no explicit when-to-use vs. when-not, no stated prerequisites (e.g. must call prebookExperienceTour first), and no routing to an alternative.

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