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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description goes further by disclosing the exact fields returned, including an 'agent_summary' string intended for LLM context injection. It stops short of describing failure behavior for an unknown txid or any network/rate-limit constraints.

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 definition is front-loaded with the core action, and the field enumeration is dense but earns its place by pre-announcing the return shape in the absence of an output schema. The trailing token-savings sentence is mildly promotional but brief.

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 no output schema, the description compensates well by enumerating the returned fields, letting the agent know exactly what it gets back. The missing piece is error/edge-case behavior (invalid or not-yet-confirmed txids) and any pagination or response-size caveats.

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?

Only one parameter, and the schema description coverage is 100% — the schema already documents txid as a 64-character hex transaction ID with min/max length enforced. The description adds nothing about txid format beyond restating 'by txid', so the baseline 3 applies while the schema carries the load.

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 a Bitcoin transaction by txid') and precisely enumerates what the returned summary contains (type, counts, fees, fee rate, confirmation/RBF/SegWit/Taproot flags). No sibling tool overlaps with transaction decoding, so the agent can select it unambiguously.

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?

It gives a clear use rationale — an agent-ready summary that 'saves 500-2000 tokens vs parsing raw TX JSON' — which implicitly routes the agent away from raw-JSON post-processing. However, it states no explicit when-not conditions, prerequisites, or error cases (e.g., unknown txid, unconfirmed tx handling).

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