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

No annotations provided, so description carries full burden. It implies a read-only listing behavior and adds the note 'Only registry addresses are real tokenized stocks,' which hints at potential data quality. While mostly straightforward, it could explicitly state it is a read operation.

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 sentences with no wasted words. Front-loaded with purpose, then usage guidance, then a clarifying note. All sentences earn their place.

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?

For a listing tool with one parameter and no output schema, the description covers scope, platform, and exclusions. It does not describe return format or pagination, but given simplicity, this is a minor gap.

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 coverage is 100% with the 'kind' parameter having an enum and description. The description adds contextual meaning by mapping enum values (e.g., 'stable' to USDG, 'wrapped_native' to WETH), which goes beyond the schema's technical labels.

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 clearly states the tool lists 'canonical tokenized stocks (Robinhood Stock Tokens), ETFs, USDG, and WETH on Robinhood Chain ID 4663' with specific verb 'list' and resource. It distinguishes from US brokerage equities, ensuring the agent knows exactly what it does.

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?

Explicitly states when to use (for tokenized equities/RWAs on Robinhood Chain) and when not ('Do NOT use for US brokerage equities'), directing to an alternative (Robinhood Trading MCP). This provides clear selection guidance.

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