get_btc_transaction_status

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

With no annotations, the description does real work: it enumerates what is returned (confirmed flag, block height, fee, size, I/O summary) and covers the mempool case. It does not state that the call is read-only, nor what happens on an unknown or malformed txid, which a zero-annotation tool should disclose.

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 first three sentences are front-loaded and informative, but the closing 'Tip: call earning_opportunities…' is filler that does not help an agent invoke this tool and dilutes an otherwise tight definition.

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, and the description compensates by naming the returned fields, which is adequate for this tool's simplicity. Missing are an explicit read-only assurance and error behavior for invalid txids, leaving a read path whose failure semantics an agent must guess.

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% and the txid parameter already documents the 64-hex-char format. The description only restates 'by txid', adding no format, encoding, or lookup-mode detail beyond the schema — 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 ('get confirmation status and details for a Bitcoin transaction by txid') and the 'Bitcoin' qualifier implicitly separates it from the generic get_transaction_status sibling. It never names that sibling or tx_status_deep, so the differentiation is left to inference.

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 statement of when to prefer this over get_transaction_status or tx_status_deep, and no prerequisites. The only situational note — 'works for both confirmed and unconfirmed (mempool)' — describes input coverage, not usage selection, and the trailing 'Tip' about earning_opportunities is unrelated promotion.

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