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

Beyond the readOnly/openWorld annotations, the description discloses a real coverage limitation ('all but the tiniest, as Curve's big list'), the result ordering (by pool size), and — critically — the commercial/auth model: $0.002 USDC per successful call via x402 on Base, Solana, or Arc, with failed calls uncharged. That is exactly the kind of cost and payment-path context annotations cannot carry.

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?

Front-loaded with the payload contents in one dense sentence, followed by the pricing clause. Every element (coverage scope, returned fields, sort order, filter, cost, payment rails) earns its place; nothing is padding.

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 an output schema present, the description needn't define return shapes, yet it still flags the 'big list' coverage caveat and the paid-call model that an agent must know before invoking. Combined with fully documented parameters, nothing material is missing for a correct call.

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 100%, so both parameters (limit with '1 to 50, default 10' and search with examples) are already fully documented in structured form. The description's 'Optional name filter' only restates the search parameter and adds no new semantics, so baseline 3 applies.

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 specific resource ('Curve Finance pools on Ethereum') and enumerates exactly what is returned: pool name, total USD value locked, and per-coin USD price and balance, sorted by pool size. This cleanly separates it from siblings like crypto_curve_gauge_weights (gauge weights) or crypto_dex_pool_liquidity (generic liquidity) without the agent needing to open a 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?

The 'Optional name filter' clause implies how to narrow results (e.g., search '3pool'), but there is no explicit when-to-use guidance, no named alternative, and no exclusions. Usage must be inferred from the purpose statement plus the pricing note, which is only implicit steering toward deliberate calls.

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