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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description still adds real behavioral detail beyond them -- output fields, a hard cap of 12 transparent outputs, mempool detail when unconfirmed, and the fact that MWEB extension data is not decoded. Minor gaps remain around pagination/error behavior for an unknown txid, which keeps it from a 5.

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?

Tight, front-loaded and segmented into purpose, when-to-use, when-not-to-use and returns. Every clause contributes a routing decision or a behavioral constraint; nothing is redundant filler.

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 no output schema, the description supplies the return shape (txid, blockhash, confirmations, blocktime, size accounting, vin_count, outputs with address and value, value_out_ltc, has_mweb_component) so an agent knows what it will get. For a one-parameter read tool this leaves nothing material missing.

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 single txid parameter already documents the 64-hex-char format via pattern and description, so the description adds no syntax or format meaning beyond it. Baseline 3 applies when the schema carries the parameter burden.

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 -- 'Look up one Litecoin transaction by txid' -- and frames it as the settlement check for an LTC payment. It also explicitly separates itself from the closest sibling (ltc_get_block), so an agent can route correctly without opening a schema.

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?

Provides an explicit 'When to use' block with concrete questions the tool answers (did the payment arrive, which block, how many confirmations, still pending) and an explicit 'Do not use' that names ltc_get_block as the alternative. It also rules out address-history lookups because the node has no address index, closing the most likely mis-invocation path.

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