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

Goes well beyond the annotations: it discloses the epistemic limits ('Missing does not prove spent', no cryptographic unspentness proof or spendability guarantee), a pre-charge validation rule ('all-absent batches rejected before charging'), and a concrete price (20 sats / US$0.02 USDC). These are exactly the caveats an agent needs to avoid over-claiming spend status, and they are consistent with readOnlyHint=false being driven by billing rather than data mutation.

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?

Three tight sentences, front-loaded with scope and return content, then the caveats, then the price. Every clause carries information; nothing is redundant filler.

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?

For a paid, open-world, read-but-billed tool with an output schema already present, the description covers scope, returned fields, epistemic caveats, rejection behavior and cost. An agent can decide to call it, form valid input, and interpret results without further clarification.

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 coverage is 100%, so all three parameters are already documented in the schema, including the l402 token format and the pay_with enum. The description restates the outpoint format and the uniqueness/cardinality rule but adds no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource — batch status for one to 25 unique Bitcoin outpoints (txid:vout pairs) — and enumerates exactly what is reported (chainstate, sequential mempool observations, value, script, confirmations, coinbase flag). The outpoint-based scope cleanly distinguishes it from the address-oriented siblings like bitcoin_address_risk and watch_bitcoin_address.

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 implied by the scope and cardinality constraint (1-25 unique outpoints) and by the note that all-absent batches are rejected, but the description never says when to prefer this over sibling tools such as bitcoin_batch_risk or bitcoin_address_risk, nor when a single-outpoint check is inappropriate. No explicit when-not guidance is offered.

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