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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses the GraphQL-to-indexer fallback path, the staleness and correctness caveat ('may be delayed or wrong'), and concrete rate-limit and pricing behavior including the exact free-tier threshold, per-call cost, prepaid batch size, and the fact that the payment-required response supplies the exact amount and payment_token. That is unusually rich behavioral context.

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 substantive answer (what fields, how fetched, fallback) is front-loaded before the compliance and billing sentences, and no sentence is redundant. The 'Education/information only; not financial advice' clause is boilerplate, but it is a single short clause rather than 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 no output schema, the description carries the burden of telling the agent what comes back, and it does so by enumerating the returned field groups. Combined with the fallback behavior and the billing/payment flow for repeat calls, an agent has everything needed to invoke it correctly without further documentation.

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 already 100%, so the pool format (BASE_QUOTE, case-insensitive, '/' or '-' accepted) is fully documented in the schema. The description still adds value by explaining the conditional lifecycle of payment_tx and payment_token — they only apply 'after the free tier' and are only obtainable from the payment-required response — which clarifies when those two optional params are actually required.

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 the resource (a DeepBook pool's parameters) and enumerates exactly which fields it returns — fees, DEEP stake requirement, tick/lot/min size, whitelist/stable flags, vault balances — which is far more than a restatement of the name. It does not, however, differentiate itself from the nearby get_pool_stats or get_mid_price siblings, so an agent must infer the boundary between them.

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 implied rather than stated: an agent can infer this is the tool for static pool configuration, but there is no explicit 'use X instead when you need Y' against get_pool_stats, get_order_book, or estimate_fees. The payment-tier paragraph describes how to pay on repeat calls, which is procedural guidance, not tool-selection guidance.

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