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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond them: closed periods are precomputed from the tool's own recording of bonding-curve trades, the open period is flagged partial, and a share of trades attributable to pump.fun's own mayhem agent is reported separately. It stops short of describing pagination/limits on the number of returned buckets.

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-loaded with what it returns, then differentiation, compare semantics, provenance, usage and pricing in a logical order. Slightly long and a touch repetitive in restating the pump_pulse relationship, but every sentence carries information an agent needs.

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?

With an output schema present, return values need no explanation, and defaults for from (14 days / 48 hours back) and to (now) are called out explicitly. Provenance, partial-period marking, comparison behavior, cost and error handling together make the definition complete for a 5-parameter, zero-required tool.

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 baseline would be 3. The description adds meaning beyond the schema by framing compare_from/compare_to as producing a second window plus a per-period change (e.g. this week vs last week), which the parameter descriptions alone do 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?

Names the specific resource (pump.fun metrics: launches, graduations, graduation rate, trades, SOL volume, unique wallets) and the slice it returns (per UTC day or hour) with an explicit compare window. It actively distinguishes itself from the sibling pump_pulse by describing itself as 'the same tape as pump_pulse, sliced into UTC days or hours' rather than a 15-minute snapshot.

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?

Contains an explicit 'When to use' clause: trends over days or hours here, last 15 minutes in pump_pulse. It also states cost ('Price: free') and error/charging behavior, leaving nothing about selection or prerequisites to inference.

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