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

Beyond the destructiveHint annotation, it discloses two-phase write behavior, the need for auth and write:bids scope, the fact that only confirm=True returns success=true, and that the server can resolve the buyer swap id. These are material mutation and authorization details an agent needs before acting.

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 front-loaded with the core two-phase workflow and uses each later sentence to cover prerequisites, identifier sourcing, exclusions, and alternatives. It is slightly repetitive in saying both 'connected resale order book' and 'live offer book', but overall it is appropriately sized for a destructive transaction tool.

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 mutation with an output schema and full annotation coverage, the description is complete enough to call correctly. It covers prerequisites, confirmation sequencing, identifier resolution, success conditions, exclusions, and alternatives.

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 100%, so parameter meanings are already well documented. The description still adds useful context by naming make_offer_on_listing as the source of bid_uuid and by reinforcing the confirm=False versus confirm=True semantics with the success condition.

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 resource: rescind an outstanding offer on an XP marketplace listing. It distinguishes this mutation tool from discovery/browse tools and from buy-now ticket purchases, and it names the related make_offer_on_listing tool for the identifier source.

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 explicitly gives when to use the tool and how to sequence calls: confirm=False first for preview, confirm=True only after explicit user approval. It also states exclusions and alternatives for browse/discovery and standard buy-now purchases.

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