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

Annotations already cover the safety profile (readOnly=true, destructive=false), and the description adds substantial context beyond them: it is free, unauthenticated, non-wallet-scoped, and it reveals on-chain state about the authorization. These are meaningful traits an agent needs before asserting to a user what this call will do.

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 defining traits (FREE, unauthenticated, non-wallet-scoped) are front-loaded well, but the final two sentences pivot to a feedback endpoint and reply policy that are not about this tool, diluting the definition and adding noise an agent must sift.

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, the description compensates by sketching what the receipt contains (seller's answer, timing, chain outcome), which is the right level of detail. Annotations handle safety, so the definition is largely complete, though the return shape is only loosely described.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'id'. The description's 'by id' and reference to a pay_send-returned id adds marginal value over the schema field text. 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 ('read') and resource ('a pay_send receipt back by id') and even describes the content of what it returns (the seller's answer, timing, and chain state). It is clearly distinguishable from the sibling pay_send that produces the receipt.

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 routes the agent to its origin ('receipt id returned by pay_send') and explains the important usage nuance that it is deliberately NOT wallet-scoped so a counterparty without your wallet can fetch it. It does not name an explicit alternative or when-not-to-use case, so it falls short of a 5.

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