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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the description earns credit for the extra context it adds: a per-caller daily quota, a capped free result set of 3 pools, and — importantly — that payment credentials must travel in MCP headers (X-Payment / X-Payment-Tx / Authorization: Bearer fg_…), not in arguments. It stops short of describing failure modes when the quota is exhausted.

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 first sentence is a strong front-loaded hook, but the content is then repeated three more times: a Chinese restatement, a [zh] block, and an [en] block that duplicates the same asset name, free-tier note and argument list. Roughly half the text is redundant, burying the one operationally critical detail about payment headers.

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?

Given no output schema, the description usefully sketches the return shape (top 3 pools with name, reserve USD, age in minutes, plus total pool count). However, with 0% schema coverage and three undocumented parameters, the argument semantics gap keeps it at minimum-viable for a tool an agent must call correctly on the first try.

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%, so the description must carry parameter meaning — but it only names the three arguments (network, limit, min_reserve) without defining them. It claims network is required and that valid values are "见说明" (see the notes), yet no value list is actually provided, and min_reserve and limit are never explained; this also conflicts with the schema showing zero required parameters and defaults of null.

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 framing — "what new liquidity pools just launched" returns the first 3 new pools with reserve and age in minutes — so an agent knows exactly what the tool produces. It does not differentiate itself from siblings like new-pools.pool_scan or yield-pools.pool_now, so it falls short of a 5.

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?

It supplies a natural-language trigger phrase and mentions the free tier (first 3 pools, daily per-caller quota), which implies when to reach for it. There are no explicit when-not-to-use conditions and no named alternative for deeper scans or for filtering beyond min_reserve.

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