List trending coins

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral context by specifying the returned data (price, volume, change, liquidity) and emphasizing the real-time 'right now' nature, which goes beyond the annotations without contradicting them.

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 concise, front-loaded sentence that clearly identifies the resource and scope. The parenthetical clarifies asset types, and the field list adds value without wasted words.

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 low-complexity, read-only tool with one optional parameter, the description adequately covers purpose and returned fields. Since there is no output schema, the field list provides the necessary insight, though it could optionally mention ordering or pagination.

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% for the single optional 'limit' parameter, including default and max values. The description adds nothing about parameters, so it relies appropriately on the schema.

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?

Description clearly states it lists trending pools on Robinhood Chain with specific data fields (price, 24h volume, price change, liquidity). It distinguishes itself from siblings like list_stock_tokens and get_chain_stats by focusing on trending memecoins/stocks as the chain's pulse.

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 phrase 'right now' and 'the pulse of the chain' clearly indicate when to use this tool: to gauge current trending activity. It doesn't explicitly name alternatives or exclusions, but the context is clear and sufficient for selection.

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