execute_booking_creation

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

Annotations cover only readOnly/openWorld/idempotent/destructive, so the description carries the rest and does: at most one write per reference, recheck target and eligibility, reconcile with fresh reads, and treat an uncertain result as requiring manual inspection rather than a retry. The two-branch confirmation protocol (confirmed: true vs omitting confirmed) is behavioral detail no annotation could express.

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 operation and precondition, then the confirmation policy branch. Dense but every clause is load-bearing except the slight redundancy between "obtain separate account-holder confirmation" and "do not ask for another confirmation."

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 need no prose. For a non-idempotent open-world write, the description supplies the missing pieces: single-write discipline, pre-write revalidation, post-write reconciliation, and the escalation path for ambiguous outcomes.

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 must compensate, and it does for both parameters: actionReference must be fresh from prepare_booking_creation, and confirmed is conditional on the resolved writeConfirmationPolicy. The only gap is that the 64-character hex pattern of actionReference and any staleness/expiry limit are left to the schema regex.

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 ("Create exactly one booking") plus a hard precondition ("from a fresh prepare_booking_creation reference"), which cleanly separates it from the prepare_* sibling that produces that reference. An agent can identify the operation and its input provenance 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?

Explicitly routes the agent: use prepare_booking_creation first, then this; read writeConfirmationRequired from preparation and the bookingCreation setting from account context to decide whether to include confirmed. It also names the exclusion — "a query or preview-only request never authorizes execution" — which is exactly the when-not guidance most definitions omit.

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