list_stock_tokens

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, providing a strong safety profile. The description adds context about the data being 'canonical' and 'live', which is mildly helpful but does not disclose further behavioral traits like pagination, rate limits, or error handling.

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?

The description is concise with two sentences. The first sentence states the primary purpose, and the second provides a usage hint. No extraneous text; efficiently 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?

For a simple list tool with filter, the description is adequate but lacks details on return format, pagination behavior, and the exact semantics of 'canonical'. Without an output schema, the agent may need more information to interpret results correctly.

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?

The description partially explains the 'query' parameter (filtering by symbol/contract substring) but provides no information about the 'limit' parameter. With 0% schema description coverage, the description fails to compensate adequately for both parameters.

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 action ('list'), the resource ('canonical stock tokens'), and the source ('Robinhood's live asset registry'). It also specifies the filtering mechanism using symbol or contract substring, which distinguishes it from sibling tools like quote_stock_trade or execute_stock_trade.

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 when needing to look up stock tokens by symbol/contract substring, but does not explicitly state when to use this tool versus alternatives. Sibling tools provide context, but the description lacks direct guidelines on when not to use it.

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