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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: reads happen on-chain in one Multicall3 call (single batched request), pricing comes from DexScreener, and unknown prices are explicitly null rather than zero - an error-semantics fact an agent cannot infer from structured fields.

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 tightly packed sentences that front-load the trigger condition and then enumerate the return shape. Nearly every clause carries information (units, symbol, decimals, price source, null handling, total); slightly dense but no wasted filler.

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-value burden and does so well: per-token balance in units with symbol and decimals, DexScreener price and USD value, null-when-unknown semantics, and a total. Only minor gaps remain, such as behavior when more than 20 tokens are supplied.

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 schema already documents all three parameters including the quote dry-run flag and the 20-token default. The description reinforces the token limit and default holdings (ETH plus tokens) but adds no syntax or format guidance beyond the schema, so the baseline 3 applies.

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 a specific verb+resource and scope: fetch holdings (ETH plus up to 20 tokens) for a Robinhood Chain address. This clearly separates it from siblings like robinhood_token, robinhood_tx, and wallet_intel, though it never names those siblings explicitly.

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?

"Use this when you need the holdings of a Robinhood Chain address" gives a clear triggering condition and the scope of what qualifies as a holdings query. It stops short of naming an alternative or stating when NOT to use it, so this is solid context without exclusions.

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