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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds useful selection context by specifying 'existing' and 'owned buyer or seller wallet', but it does not disclose error behavior, authentication expectations, or what happens when the receipt is not found. This is acceptable for a simple read tool but not rich.

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 is a single focused sentence with no filler or repetition. It front-loads the core action and includes only the essential scope qualifier about owned wallets, so every word earns its place.

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 simple one-parameter read tool with read-only annotations, the description is mostly adequate. However, with no output schema and no mention of what the response contains or where receiptId comes from, it leaves some gaps for an agent trying to use the tool without additional context.

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 description does not explicitly explain receiptId semantics, format, or how to obtain it. The parameter name is fairly self-explanatory and 'existing' implies the ID must reference an already-created receipt, providing only minimal compensation for the missing schema 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?

The description states a specific verb ('Read'), a specific resource ('existing canonical commerce receipt'), and a clear scope ('involving an owned buyer or seller wallet'). This distinguishes it from sibling tools like verify_economic_receipt or get_commerce_purchase_status by emphasizing retrieval of a canonical receipt rather than verification or status checking.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention when a canonical commerce receipt should be fetched, how to obtain a receiptId, or how this tool differs from other receipt-related or read-only tools.

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