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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds the BIP37 serialization and hex encoding, which is useful behavioral context, but says nothing about error behavior for unconfirmed or unknown txids, or the size/shape of the returned proof.

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 short paragraphs: the capability and format first, then docs link and REST route. No filler; the REST operation line is arguably redundant with the docs link but is small and useful for mapping to the API.

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 one required parameter and an output schema present, the description is nearly sufficient; the main missing element is the distinction from get_tx_merkle_proof, which is essential for correct tool selection among ~80 siblings.

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 reported as 0%, and the description only says 'for a transaction' without explaining the txid format. The schema itself supplies a 64-hex pattern and worked examples, so the agent can still construct the call, but the description does not compensate for the coverage gap.

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: fetch the merkleblock proof for a transaction, with format qualifiers (BIP37, hex encoded) and the underlying REST route. It does not, however, distinguish itself from the sibling get_tx_merkle_proof, which an agent could easily confuse with this one.

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 statement of when to use this versus get_tx_merkle_proof or get_tx_hex, and no prerequisites noted (e.g. whether the transaction must be confirmed for a merkleblock to exist). The docs link hints at context but leaves selection to inference.

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