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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds genuine value beyond that: it returns a reference plus a secure payment page, payment is online and in full, and the seat is only secured once paid — plus the confirm_duplicate escape hatch for repeat bookings. It stops short of stating refund/cancellation or payment-link expiry behavior.

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?

Dense but front-loaded: booking creation and return value come first, then the branch conditions, then the payment caveat. Every sentence carries information. It reads as one long block rather than clearly separated path/precondition/payment statements, which slightly hurts scannability.

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 18 parameters, no output schema and a non-idempotent write, the description does the heavy lifting: it explains the two booking paths, the required confirmation flag, and what the call returns. Cancellation/refund policy and payment-link expiry are omitted, which is a minor gap for a payment-generating mutation.

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 78%, just under the high-coverage threshold, but the description adds real meaning by explaining which parameters form each booking path (trip_id vs. the own-departure set) and why traveller_confirmed must be true. It does not discuss the pickup/hotel/language/notes parameters, but the schema documents those adequately.

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 ('Creates a booking for one transfer'), names the organizing entity, and explicitly ties itself to the sibling tool that produces the listings ('listed by search_transfers'). An agent can tell what this does and how it relates to the search tool 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?

Gives explicit routing rules: pass trip_id for partner departures that expose one, use from/to/type/departure_time/company for own boat departures, and do NOT use this tool for lines priced on 12Go. It also states the traveller_confirmed: true precondition, so the when-to-use and when-not-to-use conditions are both covered.

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