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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds substantive semantics beyond them: capital is size not correctness, a rate is never shipped without its denominator, no activity means not observed moving rather than quiet, sell sizes are floors. It also discloses the auth/payment model. Missing only return shape or window/pagination behavior.

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?

Front-loads the resource and return fields, which is good, but the back half compresses four distinct caveats into clipped clauses that read as dense shorthand. Every clause is informative, yet the packaging costs readability without saving much length.

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?

No output schema exists, and the description does enumerate the returned fields and their interpretive caveats, so an agent knows what comes back and how to read it. The weak spot is the unexplained 'days' parameter, otherwise this is complete for a read-only listing tool.

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% for the single parameter 'days' (default 7), and the description only alludes to 'the window' without ever stating that a window length parameter exists, its unit, or its default. It fails to compensate for the schema gap, so the agent must infer 'days' from the schema name alone.

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?

Names a specific resource (the Robinhood Chain wallets this member follows) and enumerates the returned facets: capital, record, activity in the window, fired events. An agent can distinguish this from rh_wallet_record or rh_whale_wallets without opening anything else.

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?

States the access prerequisites clearly (PumpPill membership via Bearer claim, or one x402 USDC-on-Base payment per call), which is real usage context. However it never says when to prefer this over the sibling inventory tools (rh_wallet_record, rh_whale_wallets, membership_status), so the routing guidance is only implied.

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