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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description still adds real behavioral context the annotations cannot: pricing ($0.025/call, 10 free/day, x402 options surfaced on payment-required results) and failure semantics (isError with message, not charged). What it does not add is any note on output size or latency for a multi-source bundle.

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 verdict summary is well front-loaded, but the 'When to use' sentence repeats the full server name and URL three times for pump_token, pump_dev, and pump_odds, which is pure redundancy on a single-server tool. Much of the sentence could be one clause without losing meaning.

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 specified, yet the description still enumerates the folded signals and verdict tiers. Safety is covered by annotations, cost and error behavior are explicit, and the single required param is fully documented, leaving no material gap for calling it correctly.

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?

Only one parameter and schema description coverage is 100% (base58 Solana mint, 32-44 chars, with a regex pattern), so the schema carries the parameter semantics entirely. The description adds no format or constraint detail beyond what the schema already states, making the baseline 3 appropriate.

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 concrete verb and resource plus the exact output: a 0-100 score with positives/risks, graduation odds, dev record, snipers, holders, and flow, folded into a strong/neutral/weak/avoid verdict. It explicitly positions itself as a bundle over pump_token, pump_dev, pump_odds, so an agent can distinguish it from a single-signal sibling without opening any schema.

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?

Provides an explicit 'When to use' section and names the alternatives it replaces (calling pump_token/pump_dev/pump_odds separately), with a stated selection reason: bundling is cheaper and yields one actionable verdict. The routing decision is fully determined by the description.

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