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

With no annotations, the description carries the full burden and does so well: it discloses the 20 s rewrite cadence, the 120 s staleness limit with a 503 refusal that is not charged, and the $0.01 USDC x402 payment requirement. These are exactly the operational traits an agent needs before calling.

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?

The resource and scope are front-loaded, and each subsequent sentence covers a distinct concern (returned fields, freshness, cost). It is dense with domain jargon but the clauses earn their place; the field enumeration is the only mildly redundant part given an output schema exists.

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 single-parameter, output-schema-backed tool, the description covers scope, freshness, failure behavior, and cost. The field-by-field return description is redundant against the available output schema, and no result-size or pagination limits are mentioned, leaving a small gap.

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% and the single parameter is fully documented in the schema, so the baseline is 3. The description restates the 1-240 range without adding format or default semantics beyond what the schema already provides.

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 (Solana pump.fun graduations) and a precise scope (last 1-240 minutes), and the freshness/rewrite language conveys the 'live' character. However, it never names sol_grads_history, the obvious sibling, so the live-vs-history routing must be inferred from the tool name alone.

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 through the look-back window and freshness semantics (data rewritten every 20 s, refused if stale), which tells an agent this is for near-real-time reads. There is no explicit when-to-use vs sol_grads_history or the rh_* burst tools, and no stated exclusions.

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