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

With no annotations, the description carries the full burden and does disclose the two traits that matter most: a 15-minute data-freshness lag and a hard result cap (3 bursts per chain, 3 pools). It does not state auth requirements or how the cap interacts with paging, but the staleness and volume limits are genuine behavioral disclosure.

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?

A single dense sentence, front-loaded with the defining constraint (delayed preview) and free of filler. Every clause conveys a distinct fact: delay, scope, quota, and cost.

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?

An output schema exists, so return structure need not be explained, and the description covers cost, latency, and volume limits. What is left unstated is which chains 'per chain' actually covers, a small ambiguity given the many chain-specific siblings.

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 tool takes zero parameters, so per the rubric the baseline is 4; there is nothing for the description to disambiguate beyond confirming no inputs are needed.

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 states a specific resource set: a 15-minute-delayed preview containing 3 bursts per chain plus 3 young Robinhood pools. An agent can tell this is a read-only sample/preview endpoint rather than a live feed, though it never explicitly names the sibling tools (rh_bursts_live, rh_pools_new) it mirrors in delayed form.

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?

'Free' and 'No payment' imply this is the no-cost alternative to a paid feed and is meant for a quick look rather than full analysis, but no when-to-use condition, prerequisite, or named alternative is given. Usage is left to inference from the word 'preview'.

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