Download a buyer wallet document

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds that this is a file retrieval rather than a data lookup, but discloses nothing about file format, what happens when no document is attached, or whether the document is generated on demand — gaps annotations can't fill.

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?

Two sentences, zero filler, with the primary condition front-loaded and the prerequisite id source placed after it. Every clause carries information the agent needs.

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 one-parameter read-only download with no output schema, the description covers the trigger, the resource, the outcome and how to obtain the id. The main remaining hole is the nature of the returned file (format/content type), which the agent may need to report back to the user.

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 0% and the single parameter is a bare 'id: string' with no description in the schema. The description partially compensates by explaining that the id identifies a transaction movement and by pointing to growwer_list_buyer_transactions as the source of valid values, but it never says what kind of identifier it is or how it differs from order/invoice ids used by sibling download tools.

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 the resource precisely ('the document Growwer attached to a movement of their buyer wallet') and the outcome ('returns the file'), which is enough to distinguish it from the many order/invoice/download siblings. It does not explicitly contrast itself with growwer_download_seller_transaction_document, relying on the word 'buyer' alone to make that split.

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 gives an explicit trigger ('when the user needs the document...') and, more usefully, tells the agent how to obtain the required id via growwer_list_buyer_transactions. It stops short of saying when not to use it (e.g. seller-side movements or withdrawal invoices), so it is clear guidance but not a full routing rule.

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