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

With no annotations, the description carries the full burden and delivers: fixed $0.50 USDC per pass via x402 regardless of duration, 60-minute ceiling, heartbeat cadence, event-append cadence, a 2-connection limit, auth via URL token, and the fact that a 503 stream_disabled response is not charged. That is unusually rich disclosure of cost, limits and failure semantics.

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?

Front-loads price and duration, then event types, then operational details — a sensible order with no filler sentences. It is one very dense sentence, so a comma-separated clause list would parse more cleanly, but nothing is wasted.

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 shape need not be explained, and the description covers pricing, cadence, limits and error behavior for a streaming tool. The remaining gap is routing: it does not say how this streaming pass relates to the live/history polling siblings, which is the main missing decision input.

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 there is only one parameter, so the baseline is 3. The description adds meaningful semantics beyond the schema by clarifying the pass is billed per pass and not per call, meaning the choice of minutes does not change cost — useful decision context the schema does not convey.

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 and delivery mode: a paid SSE stream at /v1/sol/bursts/stream pushing pump.fun/Robinhood Chain buyer bursts, graduations and Telegram calls. It is clear what the tool does, but it never names or contrasts the polling siblings (sol_bursts_live, rh_bursts_live, sol_calls_live) that overlap heavily with this event set, so sibling differentiation is left to inference.

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?

Usage is implied rather than stated: the 'per pass, not per call' framing hints at a choice between streaming and per-call endpoints, and details like the 2-connection cap and 503 behavior give practical context. However, there is no explicit when-to-use/when-not guidance and no named alternative for agents that only need a one-shot snapshot.

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