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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses what the verification checks (confirmations, finality, sender/receiver, value) and that expected-match checks are optional, but says nothing about permissions, rate limits, or whether the operation is read-only.

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?

Single front-loaded sentence with the core verb/resource first, followed by the verifying fields and the pricing note. No filler, though the inline query-parameter syntax is dense and slightly muddles the one-line structure.

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?

With no output schema and no annotations, the description does good work by enumerating the fields returned (confirmations, finality, sender/receiver, value), which substitutes for a return-value doc. However, the undocumented 'hash' param and the mismatch between described query params and the schema leave meaningful gaps for a paid verification tool.

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 0% and the single required 'hash' parameter is never explained in the description. Worse, the description introduces query parameters ('?to=', '?minAmount=') that do not appear in the input schema at all, creating ambiguity about the actual call surface.

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 ('Verify') and resource ('on-chain payment'), then enumerates exactly what is verified: confirmations, finality, sender/receiver, value. It's clearly more specific than generic sibling 'tx_receipt' or 'payment_evidence', but it never explicitly contrasts itself with those, so it falls short of full sibling differentiation.

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?

Usage is implied — you call this to verify a payment — but there is no explicit when-to-use, no when-not-to-use, and no reference to alternatives such as payment_evidence, tx_receipt, or should_pay despite them being obvious overlaps in the sibling list.

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