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

Annotations already cover the read-only/idempotent safety profile, and the description goes well beyond them: it discloses rate limits (100 free calls/day then 0.002 USDC/call), the prepaid batch payment flow, the payment-required response and payment_token handshake, and the caveat that data may be delayed or wrong. This is rich operational context an agent needs.

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 core purpose and returned fields, then the payment mechanics. Mostly earns its place, though 'Education/information only; not financial advice' is boilerplate that adds little operational value.

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 helpfully enumerates the returned fields and ordering, and fully explains the payment flow that several schema params depend on. An agent has everything needed 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 description coverage is 100%, so pool, limit, start_time/end_time, include_tx, and the payment params are already fully documented. The description adds no format or syntax detail beyond the schema, so the 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 verb and resource ('most recent fills in a DeepBook pool'), plus the exact returned fields (time, taker side, price, base/quote size) and ordering (newest first). The 'DeepBook pool' scoping also implicitly distinguishes it from the balance-manager sibling get_bm_fills.

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?

'Optional time range' implies the start_time/end_time use case, but no alternative tool is ever named and there is no when-not-to-use guidance (e.g., use get_ohlcv/volume for aggregates rather than raw fills). Usage is only implied.

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