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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds two genuinely useful behavioral notes beyond the schema: 'Public on-chain data only' (data provenance) and that following the money is 'slower'. It does not address rate limits or result size.

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?

A single, dense sentence that front-loads the tool's identity and then lists output categories — little waste. The enumeration of return contents is slightly long, but every clause maps to a distinct piece of information an agent would want before calling it.

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?

There is no output schema, so the description usefully compensates by enumerating the fields it returns. For a two-parameter, read-only, fully-annotated tool this is close to complete; only pagination/response-shape limits and the depth/format of the 'flags' are left unstated.

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%, and both parameters have their own schema descriptions (address pattern, follow_money semantics), so the baseline is 3. The description's 'follows the money one or two hops' mirrors rather than extends the schema's 'up and down two hops (slower)' wording, adding no new detail.

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 verb+resource ('wallet x-ray on Robinhood Chain') and then enumerates what it yields: wallet type, ETH/token holdings, Desk P&L, funders, ETH outflows, and flags. This is clearly differentiated from siblings like check_token_risk, get_price_history, or scan_contract, which operate on tokens/contracts rather than a wallet's profile and flow history.

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 implies usage (profile a wallet, optionally trace funding) but never states when to pick this over an alternative or what preconditions apply. Since no sibling performs wallet-level analysis, the omission is less costly, but the agent gets no explicit routing guidance.

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