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

With no annotations, the description carries the full burden, and it does disclose two things an agent critically needs: every call costs $0.01 via x402/USDC, and each record includes liquidity, early volume, buyers, momentum score and a go/caution/avoid verdict with reasons. It also describes the returned fields in lieu of an output schema. Missing are rate limits, pagination, and what happens on an unfunded or failed x402 payment.

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?

Three sentences, front-loaded with the resource and its scope, then the payload contents, then the filter/poll/pricing facts. Dense but every clause carries information an agent needs, and nothing is repeated from structured fields.

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 paid, read-only feed with no output schema, the description covers return contents, chain coverage, filters and cost — the essentials for correct invocation. The gaps (two undocumented parameters, no payment-failure or rate-limit behavior) are real but secondary given the tool's read-only, list-shaped nature.

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 0% across six parameters, so the description must compensate and only partly does: it explains 'minutes' (last N minutes), 'chain' (Solana, Base, Ethereum, BSC), 'verdict' (go/caution/avoid) and 'min_liquidity'. 'limit' and 'since' are never mentioned, and there is no indication of allowed values, date format, or defaults.

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 specific verb+resource+scope: a feed of newly created Solana/Base/Ethereum/BSC token pools in the last N minutes, sourced from pump.fun, Meteora, Raydium and PumpSwap. It is concrete enough to distinguish from generic search tools, though it never names or contrasts the overlapping siblings (token_pretrade_check, token_safety) that could serve the same pre-trade verdict need.

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?

'For sniping bots' and 'Poll it' give an implied use case and a polling instruction, and 'Filter by liquidity and verdict' hints at narrowing. But there is no explicit when-not-to-use, no mention of how this differs from token_pretrade_check for a single-token verdict, and no guidance on poll interval or how to avoid redundant paid calls.

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