x402_p2p_cancel

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

With no annotations provided, the description carries the full burden. It discloses the cost ($0.01 USDC), the ALGO fee (0.002), the single-transaction group structure, the need for a wallet signature, and the follow-up submit step. This is substantial behavioral information beyond what a naked tool name would imply.

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 entire description is one dense, front-loaded sentence that packs cost, transaction type, method call, fee, and workflow into a compact format. There is no wasted text; every element earns 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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description provides a complete picture: what action occurs, the transaction structure, fees, and the required next step. It does not explicitly state what the tool returns, but the sign-then-submit instruction implies a transaction object, which suffices for this complexity level.

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?

The schema already describes both parameters, with coverage at 100%. The description adds value by clarifying 'sender' is the offer maker and 'offerId' is passed directly to cancel_offer, strengthening the semantic link between parameters and the operation.

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 clearly identifies the operation as 'p2p/cancel' and specifies the exact application call 'cancel_offer(offerId)', distinguishing it from sibling tools like x402_p2p_create and x402_p2p_accept. The verb-resource pairing is precise and unambiguous.

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 provides explicit workflow guidance: sign with your own wallet and then call the submit tool. It also notes the transaction group composition and fee, giving clear context for when to use it. However, it does not explicitly state when not to use it or compare it to alternatives.

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