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

No annotations are provided, so the description carries the full burden. It does disclose the payload contents (confirmations, RBF flag, inputs/outputs), which helps an agent reason about what it will get, but says nothing about read-only nature, auth/rate limits, or behavior on unknown/pending txids. Field enumeration largely overlaps the output schema.

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 compact sentences: the resource and return facets up front, then the use case. Zero boilerplate. The middle field list is dense but each item is informative rather than 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?

With an output schema present and a single required input, the description covers purpose, contents, and use case adequately. The main residual gap is input format for the txid, which matters because a malformed hash is the likeliest failure mode.

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?

The single parameter 'txid' has zero schema description coverage, and the description does nothing to define it — no expected format (raw 64-char hex vs 0x-prefixed), no example. The word 'transaction' only implies it. Meaningful semantics are absent for the only input.

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 a specific resource (a Bitcoin transaction) and enumerates the exact facets returned: confirmation state, confirmations, block, time, fee, fee rate, RBF flag, inputs and outputs. The 'Bitcoin' qualifier naturally separates it from evm_transaction_status and tx_receipt, though it never names those alternatives explicitly.

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?

The second sentence gives concrete intent: 'confirm a BTC payment or decide whether to bump a fee,' which tells an agent when this tool is the right call. No exclusions or explicit alternative routing (e.g. bitcoin_fees for pure fee estimation) are offered.

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