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

With no annotations, the description carries the full burden and does disclose the shape of what comes back: tiered sat/vB rates, mempool size, block height, and cost of a typical payment. It also implies a read-only, side-effect-free query. It stops short of stating the data source, refresh cadence, or rate limits, which matter for a time-sensitive fee tool.

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?

Two tight sentences: the payload comes first, the usage trigger second. Nothing is padded, and the enumerated return fields earn their place by helping the agent judge whether this tool covers its need in one call.

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 parameters and an output schema exists, so the description need not explain return structure — and it already summarizes it anyway. What the agent needs to select and call correctly is present; only freshness/caching expectations for time-sensitive fee data are unstated.

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?

Zero parameters, so there is nothing to disambiguate — the baseline of 4 applies. The description correctly implies a single, parameterless snapshot call rather than any filtering options.

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?

Names the resource (Bitcoin network fee rates in sat/vB) and enumerates the exact time horizons returned: next block, 30 minutes, 1 hour, economy, plus mempool size, block height and typical payment cost. The 'Bitcoin network' qualifier implicitly separates it from EVM gas siblings like evm_gas_fees and estimate_gas, though no sibling is named outright.

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?

'Use right before sending BTC' gives a concrete usage trigger, which is more than most tool descriptions offer. However, it names no alternatives and no when-not conditions (e.g., use evm_gas_fees for EVM chains, estimate_gas for a specific transaction), leaving the routing decision to inference.

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