List Stock Tokens

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

With readOnlyHint annotations already covering safety, the description adds meaningful context about the data returned (ticker, name, contract, Chainlink feed) and the pricedOnly filter behavior. It does not disclose pagination or ordering, but the annotation lowers the bar.

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 two sentences, front-loaded with the core purpose, and includes a useful filtering tip. No fluff or redundant repetition of schema details.

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?

The description covers the essential return fields and the main filter. It does not explicitly state that all tokens are listed by default, but this is implied by 'registry' and the optional schema parameters. For a simple read-only list tool, this is adequate.

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%, so the schema already documents all three parameters. The description reiterates pricedOnly's function without adding new meaning, and limit/offset are fully covered by their schema descriptions.

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 identifies the tool as the registry of Stock Tokens on Robinhood Chain, listing key fields (ticker, name, contract, Chainlink feed). This distinguishes it from sibling search/quote tools, and the title reinforces the list operation.

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 provides a filtering guideline (pricedOnly) but does not explicitly compare to alternatives like search_token or get_stock_quote. Usage context is implied rather than stated, making it only marginally helpful for choosing between tools.

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