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

Annotations already declare the mutation profile (readOnly=false, destructive=true, openWorld=true, non-idempotent), so the description correctly focuses on behavior the annotations can't express: revalidation of the frozen destination or Square catalog, the two possible outcomes (handoff record vs. Square booking creation), and that no payment is taken. It does not say what happens when revalidation fails or how a partial/failed confirm is surfaced.

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?

Three short sentences, front-loaded with the action and its input source, then side effects, then the payment boundary. No sentence is filler — even the payment note prevents the agent from misrepresenting the flow to a user.

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?

There is no output schema, and for an open-world, destructive, non-idempotent mutation the description covers inputs, side effects, and the payment boundary well. Gaps remain around the result shape (confirmation id? handoff status?) and failure/rollback semantics after revalidation.

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 0% — the schema only says 'string, 1-200 chars'. The description supplies the missing meaning: the value is the intent produced by prepare_booking, i.e. an opaque token with provenance, not free text. It still doesn't say how long an intent stays valid or whether a failed confirm invalidates it.

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 ("Confirms one prepared booking") and anchors it to the sibling it depends on: the intent comes from prepare_booking. An agent can immediately tell this apart from prepare_booking, confirm_booking_cancellation, and the handoff-confirm siblings.

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 prerequisite (intent from prepare_booking) and the 'once' constraint are stated, which implicitly rules out retry loops. What's missing is any explicit exclusion or alternative routing — e.g. when to use check_availability first, or which of the sibling confirm_* tools handle cancellations/handoffs.

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