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

Annotations declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), and the description adds real context beyond that: the bounded two-hour recovery lock, terminalization behavior, market-first cancellation, and the rule that late finality cannot transfer a reused thing. It doesn't cover auth/permissions or failure response shape, so not a 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 core action is front-loaded in the first sentence, and the following sentences each add a distinct rule (transfer completion, lock timing, terminalization, rejection of reused things). It is dense but nearly every clause earns its place; the closing routing hint is compact.

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 stateful reconciliation tool with no output schema and a single documented-free parameter, the description supplies the key state-machine context an agent needs (lock window, terminalization, cancellation). Missing only return-value expectations and permission requirements, which keeps it short of a 5.

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?

There is a single required parameter (offer_id) with 0% schema description coverage, so the description must carry the burden. It references the 'payment_pending world offer' that the id identifies, giving implicit meaning, but never explains where offer_id comes from or its expected form.

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 verb and object: recheck a payment_pending world offer against finalized public Base records, with the outcome that a valid payment completes ownership transfer. This distinguishes it from cancel_world or payment_attempt semantically, though it relies on domain jargon ('world', 'thing') and never names those siblings directly.

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?

Usage is implied by the scenario (a payment_pending offer needs reconciliation) and by the routing hint 'Lost? Call front_door.' But there is no explicit statement of when to choose this over payment_attempt, claim_world, or cancel_world, and no stated preconditions or actor requirements, 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.