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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and openness. The description adds return content details (inputs, outputs, confirmations, block hash) but no additional behavioral caveats such as handling of unconfirmed transactions or error conditions. This adds some value but does not go beyond what is expected.

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?

Single sentence, front-loaded with the verb and object, no filler or redundant details. Every word earns its place.

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 simple 1-parameter read-only tool with annotations and no output schema, the description is adequate. It states the network, what it returns, and includes enough detail for an agent to understand its function. No critical gaps for this complexity level.

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%: the txid parameter is fully described with pattern and description. The description only says 'by txid', which adds no new meaning beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

Description clearly states 'Get full transaction details by txid on Bitcoin testnet3' with a specific verb, resource (transaction), and network (testnet3). This distinguishes it from the mainnet btc_get_transaction and other testnet tools like btc_testnet_get_balance.

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 context is clear: use for fetching transactions on Bitcoin testnet3. However, it does not explicitly name the alternative btc_get_transaction for mainnet or state when not to use this tool. No exclusions, but implied by the name and network reference.

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