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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-derivable context: the registry is the source of truth and only registry addresses are real tokenized stocks, which is a trust/verification semantic an agent cannot get from the annotations. It stops short of describing return shape or whether the registry can change.

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?

Three short sentences with zero filler: scope first, the trigger condition second, the exclusion third. Every sentence carries distinct information and the most important constraint (trust the registry) is front-loaded.

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, so the description could have said what a listed entry contains (address, symbol, kind) to fully specify the return. It compensates well on scope, safety and alternatives, but the return shape remains implicit for a tool whose whole value is the returned address list.

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 the single optional enum parameter (kind) is fully documented in the schema including the default ('all'). The description adds no filter syntax or selection guidance, so baseline 3 applies since the schema does all the work.

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 specific verb (List) plus the exact resource set (canonical Stock Tokens, ETFs, USDG, WETH) and scopes it to Robinhood Chain 4663. This separates it cleanly from stocktoken_get (single token) and from the quote/price/pool siblings without opening any schema.

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?

Gives an explicit precondition ('Use this before trusting any address'), an explicit exclusion ('Do NOT use for US brokerage equities') and names the alternative system (Robinhood Trading MCP). Both when-to-use and when-not are stated, leaving nothing to inference.

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