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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of behavior for unknown/unconfirmed txids, no error or 404 semantics, no rate-limit or upstream-availability context for an open-world external API call.

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 lines, no padding, and the docs link is front-loaded — structurally clean. But the brevity comes from under-specification rather than efficiency; nearly all the available space is spent restating the endpoint instead of adding usable information.

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?

An output schema exists, so return values needn't be described, and the annotations cover safety. Still, for a tool with a documented parameter at 0% coverage and a confusingly similar sibling, the description is too thin to let an agent invoke it confidently without reading the external docs link.

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 0% per the signals, so the description is expected to compensate, and it does not. The only parameter hint is the `{txid}` placeholder in the URL template; nothing explains format constraints (64-char lowercase hex), whether unconfirmed transactions are valid input, or what happens with a malformed hash.

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 REST path `GET /api/tx/{txid}/merkle-proof` plus the title identify the resource as a transaction's merkle proof, so the operation is inferable. However, the description never says in prose what it returns or how it differs from the near-identical sibling `get_tx_merkleblock_proof`, leaving the agent to decode the URL to understand the tool.

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 guidance on when to use this versus `get_tx`, `get_tx_status`, or especially `get_tx_merkleblock_proof`, which sounds functionally adjacent. The only usage signal is the implicit requirement that the txid be already known, which is left unstated.

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