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

With no annotations the description carries the full burden, and it does so well: it discloses rewrite cadence (every 20 s), staleness (<= 30 s behind chain), failure behavior (stale data refused with 503 and not charged), and the billing model ($0.02 USDC per call via x402). Authentication specifics and any rate limits beyond payment are the only gaps.

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?

Four dense sentences, front-loaded with purpose, costs, and freshness. Every sentence carries operational information (cost, staleness, label semantics); minor length is justified by the payment and freshness policies it must convey.

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?

Covers purpose, output meaning, freshness, failure mode, and cost — more than enough for a 3-param paid read tool that also has an output schema. The only meaningful omission is explicit routing to rh_bursts_live for real-time data.

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% with enum values and defaults fully documented, so the baseline is 3. The description adds no parameter-level detail beyond what the schema provides, but it does usefully explain the outcome fields returned.

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 and scope: 'Scored Robinhood Chain buyer bursts from the last 1-24 hours', plus what each row contains. This distinguishes it from sol_bursts_history by chain, though it never names the live alternative rh_bursts_live, leaving the live/history split to be inferred from the name.

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?

No explicit when-to-use or when-not guidance and no mention of the sibling rh_bursts_live for current data. The freshness rule ('data older than 120 s is refused with a 503') implies the tool is for recent-but-not-instant history, but the agent must infer that routing itself.

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