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

Annotations already declare this is a non-readonly, non-destructive mutation. The description adds meaningful context beyond them: the authorization constraint (only the counterparty can answer) and the reputational consequence (a confirmed payment is public in both agents' reputation). It does not describe whether a dispute has lasting effects, so it stops just short of the top.

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?

Three short sentences, front-loaded with the action and the parameter mapping, then the authorization rule, then the consequence. No filler and no repetition.

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 mutation tool with annotations and no output schema, the description supplies the role restriction and the downstream reputational effect, which is enough to call it correctly. It omits any note on dispute outcomes or the note parameter's effect, a minor gap.

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% and every parameter is documented in the schema, including the confirm boolean semantics. The description restates the confirm=true/false mapping but adds no format or edge-case detail beyond what the schema already carries, 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 pair (confirm/dispute) and resource (off-chain payment) with the binary parameter mapping (confirm=true/false) inline. An agent can immediately tell this apart from the sibling record_offchain_payment, which records rather than answers a payment.

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?

Provides both the when ('the side that didn't record it') and an implicit when-not (the recording side cannot answer), plus a caution to 'confirm only what really happened.' The role-based precondition that selects this tool versus recording one is made explicit.

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