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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context: it only returns tokens with both a feed and a pool above a minimum liquidity, the sort key, and the interpretive caveat that a premium is a measurement and never a trade signal.

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, each earning its place: usage trigger first, return/shape second, interpretive caveat last. Front-loaded and free of filler.

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 the description carries the return burden and does describe the returned fields (pool price, liquidity, quote currency, feed freshness). It is complete for the call itself, though it omits any hint of ranking tie-breaks or pagination beyond the limit parameter.

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%, so the schema already documents limit, quote, and min_liquidity_usd; baseline is 3. The description restates the minimum-liquidity filter but adds no syntax or format detail beyond 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?

The description names a specific resource and ranking (Robinhood Chain stock tokens sorted by absolute premium vs their Chainlink feed), so the agent knows exactly what list it produces. It does not explicitly differentiate from the sibling stock_token_check, so it falls short of a 5.

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?

"Use this when you want the ... stock tokens whose on-chain pools trade furthest from their Chainlink feed" gives a clear triggering condition. It offers no explicit when-not or named alternative (e.g. stock_token_check), so it stops short of a 5.

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