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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it is a paid tool at 3 sats / US$0.003 USDC per call, which affects how an agent should invoke it. It stops short of describing payment flow mechanics or response shape, so a 3 fits.

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?

Information is front-loaded: the returned payload is listed first and the pricing constraint last. The enumeration is dense but every item earns its place; the pricing sentence is compact and unambiguous.

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 carries the burden of describing return values and does so explicitly, covering all five reported metrics plus their sub-fields. The only gap is the payment workflow (when to supply l402 vs pay_with), which the schema largely handles, so it is nearly complete for a zero-parameter read tool.

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%, so both parameters (l402 token:preimage and the pay_with enum) are already documented in the schema. The description adds no meaning about how payment modes interact with the returned data, so baseline 3 is appropriate.

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 specific resource and enumerates exactly what it returns: block height, difficulty, estimated hashrate, next difficulty adjustment (blocks left, estimated change) and next halving (blocks left, estimated date). That distinguishes it from siblings like bitcoin_latest_block, bitcoin_block_stats, and bitcoin_now, which cover narrower or different slices, though it never explicitly says what makes it different from those.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only usage-adjacent content is the payment note ('paid per call'), which tells the agent nothing about selecting this tool over bitcoin_block_stats or bitcoin_now.

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