ordinals_cancel_listing

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

With no annotations, the description carries the full burden and does so well: it explains that a cancellation PSBT is requested, that the seller must sign it to invalidate the listing and reclaim the UTXO, that no extra BTC fee is required beyond the miner fee, and that an unlocked Taproot wallet is needed. It omits error conditions (e.g. listing already sold) but the core behavior is clear.

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?

Front-loaded purpose sentence, then behavior, then a numbered workflow. The trailing 'Tip: call earning_opportunities' is tangential to the task but brief and clearly separated, so it doesn't obscure the core instructions.

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 two-parameter mutation tool with no annotations and no output schema, the description covers prerequisites, what the call produces (a PSBT), and the downstream signing/broadcast path. Only failure modes and the exact return shape remain unaddressed.

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 both parameters are already documented, including the sellerAddress default. The description only restates that inscriptionId identifies the listing to delist and adds no format or edge-case detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (cancel an active Magic Eden listing for an inscription), naming the marketplace and the asset type. An agent can distinguish it from siblings such as ordinals_list_for_sale and ordinals_p2p_cancel without opening either schema.

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?

The description gives an explicit three-step workflow and names the required follow-up tools (psbt_sign, psbt_broadcast) plus the precondition of an unlocked Taproot wallet. It doesn't state when to prefer an alternative cancellation path (e.g. ordinals_p2p_cancel) or what to do if no active listing exists.

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