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

Beyond the readOnly/openWorld hints, the description discloses the upstream source, the hard scope limit (first 25 transactions of the tip block), an interpretation caveat that output totals include change, and full cost behavior ($0.002 per successful call via x402, failed calls not charged). That is materially more than the annotations convey.

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?

Sized correctly for a paid, scoped data tool: what it returns first, then the chain/scope caveats, then pricing last. Dense but every clause carries information; only the change-vs-transfer note is slightly redundant with the scope limit sentence.

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 an output schema present the description needn't enumerate return values, yet it still covers chain restriction, sampling limit, interpretation caveat, and payment mechanics — everything an agent needs to decide and call 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%, so the baseline is 3, but the description adds real meaning: minBtc is framed as a total-output threshold and the returned total is clarified as transaction size rather than a single wallet's transfer, which changes how the agent should read results. The 25-cap also reinforces the limit parameter's upper bound.

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 data source (mempool.space), resource (large transactions in the tip block), returned fields (output total, fee, txid, block height) and an explicit chain restriction (Bitcoin only, no ETH/SOL), so the agent knows exactly what it gets. It stops short of contrasting itself with the adjacent mempool-stats tools, so differentiation is implicit rather than stated.

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 only implied: 'large transactions' plus a minBtc filter signal a whale-watching use case, and the 25-transaction cap hints at a sampling tool. There is no explicit when-to-use guidance and no named alternative such as crypto_bitcoin_mempool_stats or finance_mempool_bitcoin, which sit right next to it in the catalog.

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