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

Annotations already declare write, idempotent, open-world, non-destructive behavior, but the description adds substantial context beyond them: a five-minute city reservation, a separate two-hour recovery window, the payment_pending state, and a no-double-pay retry guarantee. It does not describe response shape or error semantics beyond the deadline, keeping it at a strong 4 rather than 5.

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 five dense sentences with no filler, and the primary flow is front-loaded before the recovery-window detail and fallback. The jargon-heavy phrasing ('1F3EA', 'city reservation') slightly reduces immediate clarity, but overall it is efficiently structured.

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 multi-step payment tool with no output schema and incomplete parameter descriptions, the description covers the critical lifecycle: reservation timing, signed retry, payment_pending recovery, and a fallback tool. It leaves gaps around offer_id semantics and final settlement outcomes, but the behavioral flow is largely complete.

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%, so the description must compensate fully. It clarifies buyer_wallet and likely market_checkout_id ('checkout ID'), but the required offer_id is never explicitly explained, and the description does not disambiguate which identifier is the offer versus the checkout. Partial compensation for a zero-coverage schema warrants a 3.

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 uses a specific verb phrase ('Reserve or pay for') and a specific resource ('1F3EA world offer'), so an agent understands the core operation. However, '1F3EA' is opaque jargon and the description never distinguishes this tool from likely siblings such as payment_attempt or reconcile_world, which limits sibling differentiation.

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 provides a procedural sequence (send checkout ID and buyer wallet first, then retry with X-PAYMENT) and a fallback ('Lost? Call front_door'), which implies usage. But it gives no explicit when-to-use vs when-not-to-use relative to payment_attempt, reconcile_world, or cancel_world, leaving the agent to infer selection.

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