Trending tokens on Robinhood Chain

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

readOnlyHint=true already declares the safe read profile, so the bar is lower. The description still adds value by declaring that results are live, scoped to 24h, and carry specific fields (price, 24h change, market cap, volume, explorer link), which tells the agent what data to expect. Pagination, rate limits, and result-size limits are not addressed.

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?

One sentence, front-loaded with the resource, then the variants, then the returned fields. No redundant or filler text.

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?

There is no output schema, so naming the returned fields in the description is the right compensating move, and the chain/24h scope is stated. For a single-optional-parameter read tool, nothing material is missing.

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% and the single 'list' parameter already has an enum and description, so the schema carries the parameter burden. The description does add that gainers/losers are measured over 24h, but offers no further semantics beyond that.

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 resource (trending tokens) plus the three concrete list variants and the 24h window on Robinhood Chain, so it is clearly distinct from single-token siblings like robinhood_token_info and robinhood_token_safety.

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 this is the discovery screen for token lists, but it never says when to prefer it over robinhood_token_info or robinhood_token_safety, nor any exclusions or prerequisites. Selection guidance is left to the enum in the schema.

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