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

Annotations mark this as a non-destructive, idempotent write, and the description reinforces that with 'Creates intent only, never a booking, charge', telling the agent no money moves and the side effect is bounded. The clientKey retry guidance also explains idempotency behavior in practical terms. The unexplained phrase 'enforces zero-only' is opaque jargon that dilutes otherwise strong disclosure.

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 access restriction is usefully front-loaded and there is little wasted text, but the compression goes too far: 'enforces zero-only', 'AMC call' and 'booking assistant' assume context the reader may lack. Sentences are fragments rather than a structured explanation, so density comes at the cost of comprehensibility.

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 4-parameter tool with a required nested flexibility object and an output schema, the definition covers the essentials: who may call it, when to call it, what it does and does not do, and how the two showtime paths relate. Remaining gaps — filmId semantics, the meaning of 'zero-only', and whether queued intents expire — are minor adjacent details rather than blockers.

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?

With 0% schema description coverage, the schema itself conveys only structure, so the description must carry the load. It does add crucial non-schema meaning: clientKey is for retries and selectedShowtimeId and flexibility are alternatives ('OR'), which is the key constraint. However, filmId is never mentioned, and 'complete flexibility' (that every flexibility subfield is required) is left implicit, so compensation is only partial.

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 states a specific action and result: it 'Creates intent only, never a booking, charge or AMC call', plus 'Explicitly request a booking' in the title, so an agent understands this queues an intent rather than completing a purchase. 'Your booking assistant alone executes it' clarifies that fulfillment is downstream. It never names the sibling cancel_booking_request, but the intent-vs-execution distinction is clear enough.

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?

It gives a hard precondition — 'Only call when the human explicitly asks to queue a booking' — and an access restriction, 'Private executor accounts only'. It also tells the agent how to satisfy the call: 'Supply a selected showing OR complete flexibility'. What it lacks is an explicit statement of when not to use it or which sibling to prefer (e.g. search_showtimes/get_best_showings to find a showtime first).

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