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

Beyond the annotations (readOnly, openWorld, non-idempotent), the description discloses the two facts an agent most needs and cannot get elsewhere: this tool costs $0.005 per call and payment is settled via x402 in USDC on Base or Arbitrum One. It also states the data provenance (reconstructed from chain event logs) and the keyset ordering basis, which sets expectations about determinism during pagination.

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?

Four dense sentences, front-loaded with the resource and event scope before parameter mechanics and cost. Nearly every clause carries weight, with only the 'not financial advice' disclaimer being questionable filler for an agent audience.

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?

No output schema exists, yet the description still reveals the pagination contract (data.next_cursor) and the ordering, which is exactly the return-shape detail an agent needs to loop correctly. Combined with cost, payment rail, and data provenance, nothing material for correct invocation is missing for a three-parameter read-only tool.

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%, so the baseline is 3, but the description adds real meaning: the token parameter's ticker example (NVDA) versus a 40-hex contract address, and the fact that the cursor is opaque and keyset-based on block plus log index rather than a simple offset. Limit clamping behavior is left to the schema, which handles it adequately.

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 opens with a specific verb and resource — auditing when a stock token's supply was created or destroyed — and enumerates the event types (mint, burn, issue, redeem, transfer) with a defined ordering (newest first). That cleanly separates it from aggregate-style siblings like token_summary and token_snapshot, though it never names those siblings explicitly.

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 gives solid invocation guidance — pass a ticker like NVDA or a contract address, page with the cursor — but this is how-to-call guidance rather than when-to-use guidance. There is no statement of when to prefer token_snapshot, token_summary, or find_token instead, and no exclusions.

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