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

Annotations already declare readOnlyHint/non-destructive, so the description correctly spends its budget on semantics instead: OAuth scope, Passkey-only exclusions, and the critical caveat that the compatibility balance is NOT Direct Pay principal or Base-mainnet USDC escrow. It stops short of stating data freshness or how many 'recent' refunds are returned, which matters since there is no output schema.

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?

Compact and front-loaded with READ-ONLY, with no filler sentences. However, the semicolon-dense fragment style and shorthand like 'webaz_buyer_orders full=true' reduce parseability for an agent skimming the definition.

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 parameters and no output schema, the description must carry the full burden of describing what comes back, and it does list the returned elements plus interpretation caveats. It is missing return-shape details such as currency units, refund window/count, and freshness, which are the remaining gaps for a tool with zero structured documentation of its response.

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?

Zero parameters, so there is nothing for the description to disambiguate. The description correctly does not invent parameter-like guidance; the one embedded call hint (webaz_buyer_orders full=true) is a routing note, not a parameter of this tool.

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 concrete verb+resource+contents: a read-only wallet view returning balance, escrow, and recent refunds. It also distinguishes a sub-case (per-order refund_status belongs to webaz_buyer_orders). The phrase 'wallet_read_minimal OAuth view' is internal jargon that adds noise rather than clarity, keeping it short of a 5.

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?

Explicit exclusions are given (no withdrawals, receive accounts, transfers, or credentials) and one sibling is named as the alternative for per-order refund status. It does not contrast with other wallet-adjacent siblings like webaz_address or webaz_connection_status, but the when-not guidance is unusually concrete.

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