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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds real behavioral consequences on top — ownership transfer on valid finality, a bounded two-hour recovery lock, market-first cancellation after terminalization, and the reused-thing and pre-end-evidence edge cases. It never states what the tool returns or whether repeated calls after terminalization are safe, which keeps it from 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 lead sentence is correctly front-loaded and the outcome conditions do earn their place, but the middle sentences are compressed to the point of ambiguity ('a valid payment moves the remnant whole to the buyer') and 'Lost? Call front_door' reads as filler in a definition that needs to be operational.

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 destructive, open-world mutation tool with no output schema, the description covers the important decision branches (valid finality, ambiguous evidence, late finality, post-terminalization). The remaining gaps — how to source the offer_id and what a failed or ambiguous reconcile returns — are real but narrower than the coverage it does provide.

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% for the single offer_id parameter, so the description must carry the meaning. It implies offer_id identifies a 'payment_pending world offer', but never says where to obtain that id, whether non-pending offers are rejected, or what the integer encodes — partial compensation only.

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 first sentence states a specific verb and resource: 'rechecks a payment_pending world offer against finalized public Base records', which distinguishes it from siblings like cancel_world, payment_attempt, and claim_world. The jargon ('world', 'thing', 'remnant') is domain-heavy but the core action is identifiable.

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 precondition 'payment_pending' rather than stated as an explicit when-to-use rule, and there is no contrast with cancel_world or payment_attempt despite them being obvious alternatives. The closing 'Lost? Call front_door' is the only explicit routing, and it targets a generic help tool rather than the relevant siblings.

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