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

Annotations already establish read-only and open-world behavior, so the bar is lower; the description nonetheless adds material context beyond them: this is a point-in-time snapshot with no historical retention, and the pricing/cost model ($0.002 USDC per successful call via x402, no charge on failure). The payment rails and failure-charging rule are exactly the kind of behavioral detail annotations cannot express.

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 payload metrics are front-loaded in a single dense sentence, followed by the snapshot limitation and pricing as secondary clauses. It is efficient, though the metric enumeration is list-like and slightly crammed.

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?

A rich output schema exists, so return-shape explanation is correctly omitted; the description instead covers scope (snapshot only) and cost. For a parameterless external-data tool, this is nearly complete, with only minor room for clarifying freshness/update cadence of the snapshot.

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 the baseline is 4; there is nothing for the description to disambiguate beyond what the empty schema already conveys.

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 exact resource (Bitcoin mempool congestion) and its source (mempool.space), then enumerates the specific metrics returned: unconfirmed tx count/size, recommended fee rates in sat/vB, difficulty-adjustment progress and retarget date, and blocks to halving. This is specific enough to separate it from adjacent siblings such as crypto_bitcoin_hashrate_difficulty, which covers mining stats rather than mempool state.

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?

The phrase 'Current snapshot only; no history' tells the agent this is unsuitable for time-series work, which is useful. However, no sibling is named as an alternative for historical fee data, and no conditions (e.g., when congestion matters versus when hashrate/difficulty stats are wanted) are stated.

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