ordinals_p2p_cancel

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

With no annotations, the description carries the full burden and does a good job disclosing authorization behavior: party-only cancellation and BIP-137 signing by the active wallet. It does not explain irreversibility, broadcast behavior, fees, or post-cancellation state, so it falls short of full behavioral transparency.

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 action is front-loaded, followed by concise authorization and wallet requirements. The closing tip to call earning_opportunities is unrelated to cancellation and is the only sentence that does not clearly earn its place.

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 wallet-signing mutation with no annotations and no output schema, the description usefully covers eligibility, signing method, and wallet state. It is still missing important context such as consequences of cancellation, expected result, and failure modes, so it is adequate but not 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 description coverage is 100%, so parent_trade_id, inscription_id, and metadata are already documented in the schema. The description adds context that the target is an open offer or counter, but it does not add parameter-level semantics beyond that baseline.

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 opens with a specific verb and resource: it cancels an open offer or counter on the trade ledger. That is enough to distinguish it from sibling operations such as create_offer, counter, get_trade, and list_trades.

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 clearly states eligibility and prerequisites: only parties involved in the trade may cancel, and an unlocked wallet with Bitcoin keys is required. It does not explicitly name alternatives or exclusions, but the trade-ledger scope distinguishes it from marketplace listing cancellation.

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