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

Annotations already cover the safety profile (readOnlyHint, idempotent, not open-world), so the bar is lower. The description adds genuinely useful non-schema behavior — that confirmed transactions in the last 6 blocks report confirmations, and that the call is metered (5 sats / US$0.005 per call). It does not discuss error behavior for unknown txids or how unconfirmed vs. deep-confirmed data differ beyond that one clause.

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 sentences, both front-loaded with the substantive output list before the payment note; nothing is buried. Minor redundancy in 'Paid per call. Price: ... per call,' which says the same thing twice.

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?

There is no output schema, so the description has to carry the return-value burden and does: it enumerates the four result components plus the confirmations case. Payment flow and pricing are covered. The only real gap is failure/edge behavior (unknown txid, transactions older than the 6-block window) for a three-parameter paid 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 txid, l402, and pay_with are already documented at the parameter level; baseline 3 applies. The description's 'paid per call' and price statement give useful context for the payment parameters but add no syntax or format detail beyond the schema.

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 concrete resource (a Bitcoin transaction) and enumerates exactly what the tool reports: effective cluster-chunk fee rate, projected block, next-block fee rate, and the RBF/CPFP fee needed to accelerate. That is far more specific than a generic 'ETA' tool. It does not, however, explicitly distinguish itself from the sibling bitcoin_transaction_status, which an agent could easily mistake for this.

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?

Usage is only implied: an agent can infer this is the tool for 'when will my transaction confirm and what fee fixes it'. There is no statement of when NOT to use it, no pointer to bitcoin_transaction_status or bitcoin_fee_estimates as alternatives, and no mention of what happens for very old or unknown transactions.

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