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

The description adds meaningful behavioral context beyond the annotations: it clarifies that this creates an unpaid reservation, does not charge or confirm the booking, and requires real customer data. It also implies a checkoutUrl in the response. The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description reinforces these without contradicting them. It does not mention idempotency behavior explicitly, but that is covered by the annotation.

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 description is a single dense paragraph with no filler. It front-loads the primary purpose and then lists prerequisites and side-effect clarifications. Every sentence adds value, though some technical jargon (submissionId, resumeToken, opaque capability) could be more accessible. It is appropriately concise for the tool's complexity.

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 tool with 6 parameters, nested objects, and an output schema, the description is incomplete. It fails to explain the ride object's purpose or required fields, the meaning of locale, or how the output checkoutUrl is returned. It does mention that the customer confirms on checkoutUrl, but does not clarify that this is part of the response. The 'Essential one-way transfer' limitation is also unaddressed in the schema, leaving agents uncertain about tripType. Given the lack of schema descriptions, the description leaves too much to inference.

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 0%, so the description is the sole source of parameter meaning. It mentions submissionId, resumeToken, contact, and distributionPartnerCapability (as 'opaque capability'), but it does not explain the 'ride' object fields, 'locale', or the constraints of any parameter. The schema itself has no descriptions, so an agent would be left guessing about required subfields and formats beyond the JSON structure.

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 clearly states the verb ('Prepare'), the resource (a binding offer), and scope ('exactly one unpaid reservation and binding offer for an Essential one-way transfer'). It also explicitly notes that it does not charge or confirm, which distinguishes it from a booking action. However, the phrase 'Essential one-way transfer' conflicts with the schema's tripType enum that allows both 'one_way' and 'return', creating ambiguity about whether this tool supports round trips.

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 description lists prerequisites ('Requires real customer contact data and a client-generated submissionId and resumeToken') and a conditional ('Approved distribution partners may add their opaque capability'). It does not explicitly name sibling tools like quote_ride or get_offer_status, nor does it state when to prefer this tool over alternatives. The context implies it is for finalizing a binding offer rather than getting a quote, but that is not spelled out.

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