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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses important behavior: the tool is paid ($0.002 USDC per successful call via x402 on Base, Solana, or Arc), failed calls are free, and some API-reported liquidity values are implausible and intentionally uncorrected. These are exactly the kinds of cost and data-quality caveats an agent needs before invoking the tool.

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 description is compact and front-loaded: it begins with the resource and ordering, then lists fields, then caveats, then pricing. Every clause carries useful information, with no filler or redundant restatement.

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 simple one-parameter, read-only, open-world data tool with an output schema, the description is complete. It covers what is returned, the result cap, data-quality caveats, and payment behavior, so an agent has enough context to call it correctly.

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 limit parameter is fully documented in the schema, including its 1-to-20 range and default of 5. The description's mention of 'Top 1 to 20' reinforces the schema but does not add new syntax or selection meaning, so the baseline of 3 is appropriate.

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 clearly states the resource and scope: Balancer V2 pools ordered by total liquidity in USD, with an explicit list of returned fields and a 1-to-20 cap. It does not explicitly differentiate the tool from adjacent siblings such as generic DEX pool liquidity or Curve pool tools, so it falls short of a 5 despite being clear on its own.

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 description gives a scope and a result limit, but it does not say when to choose this tool over alternatives like crypto_dex_pool_liquidity or finance_curve_finance_pools. An agent is left to infer usage from the resource name rather than from explicit guidance.

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