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

Goes well beyond the readOnly/openWorld annotations by disclosing the pricing model (100 free calls/day per client, then 0.002 USDC per call), the prepaid batch mechanism (~0.01 USDC), and the two-step flow where a payment-required response returns the exact amount and a payment_token. It also warns that data 'may be delayed or wrong.' Annotations already cover safety, and this adds rate limits, cost, and a payment handshake the agent must sequence correctly.

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?

Single dense paragraph with the core purpose front-loaded and the operational/payment caveats following. The disclaimers ('education/information only; not financial advice') consume space without helping tool selection, but nothing is redundant enough to be disqualifying.

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 correctly previews the return payload (base/quote assets, tick, lot, min size) and explains the payment-required response shape. Combined with rich annotations, this is nearly complete; only the lack of any pagination or result-volume hint keeps it from a 5.

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 all four parameters are already documented in the schema. The description adds only marginal meaning (human units, asset filter framing) and largely restates the payment flow the schema already describes. Baseline 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?

States a specific verb and resource: 'List Sui DeepBook v3 spot pools with base/quote assets and trading params (tick, lot, min size in human units).' An agent knows exactly what comes back. It does not, however, distinguish itself from near-neighbors like get_pool_params or get_pool_stats, so the differentiation half of the 5-bar is unmet.

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 tells the agent the asset filter is optional and that payment params apply only after the free tier, which is genuine usage context. But it never says when to choose this over get_pool_params/get_pool_stats, so the when-not/alternatives bar is not reached.

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