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

Beyond readOnlyHint it discloses meaningful behavior: the data is untrusted citizen-authored content, addresses are financial data and never payment instructions, and CallToolResult _meta carries a server-owned provenance boundary. The 'READ-ONLY: this call changes nothing' sentence partly restates the annotation, but the provenance and prompt-injection warnings add real value.

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?

Purpose is front-loaded in the first clause, followed by mode selection and safety notes in descending priority. It is dense but each sentence carries weight, with only minor redundancy in the closing READ-ONLY restatement.

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?

No output schema exists, so the description carries the return-value burden, and it does so reasonably (preview rows, canonical hash payload, provenance in _meta). Gaps remain around since_id semantics and pagination, but for a read-only listing tool the coverage is largely adequate.

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 only 33% (binding_id is the sole documented param), so the description must compensate. It clarifies binding_id (full canonical record vs preview page) and docket (preview filtering), but leaves since_id entirely unexplained in both schema and description.

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 (Read) and resource (scoped payout authorizations plus their independently reproduced receipts) with the settlement asset named (USDC or 1F916). It does not explicitly distinguish itself from nearby siblings like payout_binding, payout_receipt, or payout_wallets, so an agent must infer the boundary.

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 description explains the two invocation modes ('Pass binding_id for the complete canonical hash payload, or filter preview rows by docket'), which is really parameter-mode guidance rather than when-to-use guidance. It names no alternative sibling tool and states no conditions under which this tool should be avoided.

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