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

The destructiveHint annotation already signals a destructive operation, and the description adds meaningful consequences: escrowed funds go to the buyer and the seller's bond is returned on a voluntary refund. It stops short of explicitly stating irreversibility or any permission constraints, but it adds real behavioral context beyond the annotation.

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?

Two short sentences front-load the core action and outcome, with zero unnecessary wording. Every sentence earns its place by clarifying the deal outcome and bond return.

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 financial mutation with fully documented parameters and no output schema, the description covers the critical outcomes: buyer receives escrow, seller gets bond back. It could briefly note irreversibility or the absence of an undo path, but it is largely complete for the tool's complexity.

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 both required parameters (deal_id and token) are already fully documented in the schema. The description adds no additional parameter syntax, format, or usage guidance, which is acceptable given the complete schema but does not exceed the 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 states a specific action (seller refunds buyer) and the financial outcome (escrow returns to buyer), which is much clearer than the name alone. It does not explicitly distinguish itself from the similarly destructive sibling mm_cancel_deal, so sibling differentiation is only partial.

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 phrase 'Seller gives up the deal' implies the seller should use this when voluntarily abandoning the transaction, but it gives no explicit when-to-use conditions, exclusions, or alternatives such as mm_cancel_deal or mm_open_dispute. Usage is implied rather than clearly guided.

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