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

The annotations already declare non-destructive, idempotent, and open-world behavior, and the description usefully adds what verification occurs: it reads the receipt on chain, checks that it came from the prepared wallet, and matches the prepared transaction. It also states that no funds move on chain and that a signed payment record is returned for the audit trail. The phrase 'read-only on chain' sits alongside readOnlyHint=false, but because it is explicitly scoped to on-chain activity, it does not directly contradict the annotation; the off-chain record creation could still be clearer.

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 description front-loads the trigger condition, then explains the verification and the returned record, and closes with the on-chain safety note. Three sentences, each carrying useful information without restating schema details.

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 confirmation tool with no output schema, the description covers the prerequisite, the required inputs, what is verified on chain, what is returned, and the no-fund-movement guarantee. It does not describe failure or mismatch outcomes, leaving a small gap for an open-world tool that reads an on-chain receipt.

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%, and the schema documents all three parameters, including the optional contribute flag. The description reiterates prepare_id and transaction hash but adds no format or semantic detail beyond the schema, and it does not mention contribute. With the schema doing the heavy lifting, the baseline score of 3 is appropriate.

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 verb and resource, 'confirm' a 'payment', and explicitly positions the tool after prepare_payment has been used and the wallet has broadcast. This distinguishes it from prepare_payment and other siblings, so an agent can identify the correct post-broadcast verification step immediately.

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 specifies the trigger: call this after your wallet has sent a payment prepared by prepare_payment, and provide prepare_id plus transaction hash. It does not name alternatives such as submit_payment, reconcile_payment, or track_payment_settlement, nor does it state when not to use this tool, so it falls short of a full 5.

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