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

Beyond the annotations (already covering read-only, idempotent, non-destructive, closed-world), the description discloses freshness semantics that materially affect how results should be trusted: near-real-time (within 10 seconds) for coins traded in the last 12 hours, otherwise an hourly fill. It also states the data source, the 50-coin ceiling, the 'Free' cost, and that values are returned in both SOL and USD.

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?

One dense sentence plus a short 'For:' list, front-loaded with 'Free.' and then the core capability. Nearly every clause carries information (source, staleness, cap, currencies), though the freshness clause is packed tightly enough that it takes a second read.

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 no output schema, the description correctly takes on the job of saying what comes back: market cap and price, in SOL and USD, with a freshness qualifier. What it omits is edge behavior — what is returned for mints that never traded, unknown/invalid mints, or how missing entries appear in the response.

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 the single parameter is documented in-schema (base58 mint addresses, min 1 / max 50). The description repeats the 'up to 50' limit but adds no new meaning about input format, ordering of results, or how partially-invalid mint lists are handled. Baseline 3 applies when the schema already carries the parameter burden.

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 gives a precise verb-and-resource pair: it returns current market cap and price for up to 50 pump.fun coin mints, and it names the underlying data source (bonding curve last trade or the coin's own PumpSwap pool). That is far more specific than the tool name alone. It does not, however, distinguish itself from coin-related siblings such as check_coin or find_coin, so an agent must infer the boundary.

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?

The 'For:' clause gives concrete triggering questions ('what is this coin's market cap', 'price of these coins', 'is it still trading'), which is a genuinely useful routing cue. It stops short of naming a when-not condition or an explicit alternative tool, so the agent gets positive guidance but no exclusions.

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