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

Annotations already cover readOnly, idempotent and openWorld=false, and the description adds what they cannot: data provenance ("from this node's own Bitcoin Core"), a paid per-call model, and the exact price in sats and USDC. It omits payment failure/expiry behavior, which the schema only partly addresses.

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 enumeration is front-loaded in the opening clause and payment terms are compactly stated in two short sentences with no filler. The first sentence is dense but every listed item tells the agent what is returned.

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 no output schema the description must carry the return-value burden, and it enumerates every section including the fee range (1 to 1008 blocks) and halving/retarget details. Only response format and payment-failure handling are unstated, which is minor for a zero-required-parameter aggregate read.

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 description coverage is 100% and both parameters including the enum are fully documented in-schema, so the description cannot add much. It contextualizes the payment parameters by stating the per-call price, but adds no syntax or sequencing detail. Baseline 3 applies.

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?

"Bitcoin right now in one call" names the resource and enumerates the four payloads (fee estimates, mempool size, latest block, network status), so an agent knows exactly what it returns. It differentiates from single-topic siblings only implicitly via "in one call" rather than naming them, keeping it short of a 5.

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?

No explicit when-to-use or when-not guidance and no sibling is named, despite bitcoin_fee_estimates, bitcoin_mempool_blocks, bitcoin_latest_block and bitcoin_network_status each covering a subset. "In one call" implies the aggregation use case, which is enough for implied usage but leaves routing to inference.

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