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

Annotations already cover read-only and open-world flags, but the description adds genuinely non-redundant behavior: the live data source, the per-call cost of $0.002 USDC, the x402 payment rails (Base, Solana, Arc), and that failed calls are not charged. The only gap is no note on freshness/refresh cadence or rate limits, but the cost and failure-charging disclosure is well above the annotation bar.

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?

Three sentences, front-loaded with what the tool returns before the caveat and the pricing detail. Every sentence carries information, though the payment sentence is dense and could be trimmed without losing meaning.

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, return-value explanation is not required, and the description covers source, contents, and cost. However, for an open-world live-data tool it omits data freshness/staleness guidance and doesn't distinguish itself from the closely named mempool sibling, leaving a real decision gap for the agent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the documented baseline of 4 applies. Nothing in the schema needs compensating for.

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 a specific source (mempool.space) and specific payload (recommended fee rates for fastest/half-hour/hour/economy plus chain tip height), so the agent knows exactly what it returns. It partially differentiates from price-oriented siblings via 'Live network data; no prices', but never addresses the near-duplicate crypto_bitcoin_mempool_stats sibling.

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?

'Live network data; no prices' implies this is for fee/height lookups rather than price data, which is weak routing guidance. It gives no explicit when-to-use or when-not and does not name an alternative tool, leaving the agent to guess against crypto_bitcoin_mempool_stats and crypto_bitcoin_hashrate_difficulty.

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