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

Adds substantial context beyond the annotations: the URL must not be opened, fetched, or followed by the agent (it is for the customer's own browser) — a non-obvious behavioral constraint the annotations do not express. It also explains the deposit_taken outcome and that the balance is due at the visit, clarifying the business state behind the readOnlyHint=false annotation. No contradiction with 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 return shape in the first sentence, then the critical safety instruction, then the sequencing and deposit caveat. Every sentence carries distinct information; nothing is repeated from the title or schema.

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?

An output schema exists so return values needn't be restated, yet the description still summarizes the business content of the response. It covers sequencing, the non-follow-the-URL rule, and the deposit-paid branch — everything an agent needs to call and act on this correctly.

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%, with both slug and offer_id documented, including that offer_id is 'returned by get_quote'. The description only reiterates that provenance ('once get_quote or a booking flow has produced an offer_id') without adding format or constraint detail. Baseline 3 is appropriate since the schema carries the load.

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: returns a plain-text summary of a priced offer plus a customer-facing URL on the vendor's domain. It also enumerates exactly what the summary contains (service, amount, currency, cancellation policy, price validity), so an agent knows the payload without opening the schema. Clearly distinct from siblings like get_quote (which produces the offer) and create_booking_payment_link (which collects payment).

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 an explicit precondition — 'Use this once get_quote or a booking flow has produced an offer_id and the user is ready to review or continue'. It also names a specific negative case with the sibling involved: if the deposit was already paid via create_booking_payment_link, don't send the person to pay again. Both when-to-use and when-not-to-use are covered.

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