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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description does add genuinely useful context beyond that: it is a paid call at $0.09 USDC per invocation and payment credentials must travel in MCP headers (X-Payment / X-Payment-Tx / Bearer), not as parameters. It also lists the risk flag vocabulary (thin_liquidity / no_buys_5m), which helps interpret results.

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 text is a bilingual block that repeats the same content in Chinese and English, includes a dangling reference ('参数同左' / 'params same as left'), and buries the payment-header instruction at the end. The field enumeration in the opening sentence is useful, but overall it reads as marketing copy rather than a front-loaded definition.

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 does the right thing by enumerating the returned fields and risk flags, and it covers the payment requirement. However, for a three-parameter tool with zero schema documentation it leaves the parameters unexplained and gives no basis for choosing it over new-pools.latest_pools.

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% — the three parameters (network, limit, min_reserve) appear only with titles and null defaults. The description merely restates the parameter names ('Args: network, limit, min_reserve') without adding accepted network identifiers, limit bounds, or reserve units, so it fails to compensate for the schema gap.

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 and action: scanning newly launched liquidity pools, and enumerates the returned fields (pool address, price, reserve, 1h volume, 5m buy/sell counts, pool age, risk flags). This is far more specific than the bare name, though it never distinguishes itself from the sibling new-pools.latest_pools, so an agent cannot tell which of the two to pick from the text 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 only implied through the framing question 'what new liquidity pools just launched', which gives the agent a rough trigger condition. There is no statement of when-not to use it, no prerequisite conditions, and no mention of the obvious alternative new-pools.latest_pools.

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