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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false), so the description's value is in the extra context it adds: it discloses cost ($0.03 USDC on Base, or plan key), a 100-wallet coverage limit, and the negative-result behavior (found:false) still billed. That is substantive beyond the annotations, though it does not describe error modes or return shape in detail.

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 and metrics are front-loaded, and the sentences are dense with no filler. The pricing is stated twice ('Costs $0.03 USDC on Base. (paid $0.03, or included in a RobinX plan key…)'), a minor redundancy that keeps it from a 5.

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 carries the return-shape burden and does so reasonably (PnL, win rate, hold style, open bags marked two ways). Coverage, pricing, and the unknown-address case are all covered, and as a read-only tool there are no mutation or reversibility concerns to disclose.

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 100%, so the address parameter is documented structurally. The description adds meaningful semantic constraint beyond the schema: only addresses within the tracked 100-wallet roster are valid, and outside ones yield found:false. That is real parameter-domain information, above the baseline-3 for fully covered schemas.

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 ('Chain-derived trading record for a Robinhood Chain wallet') and enumerates the specific metrics returned (realized PnL in WETH across v2/v3/v4, win rate, hold style, open bags). Naming the chain distinguishes it from the robinx_solana_wallet_receipt sibling without either schema being opened.

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?

Usage is implied by the scope (Robinhood Chain wallet, tracked roster of 100) but there is no explicit when-to-use/when-not or named alternative to route on. The roster and found:false note hint at the valid domain, but the agent must infer selection vs the Solana receipt itself.

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