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

Annotations already establish readOnlyHint=true, so the safe-read profile is covered. The description usefully discloses the return contents (result, height, proof), which matters because there is no output schema, but it says nothing about errors, missing-hash behavior, or the odd idempotentHint=false setting. Adequate but not rich.

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 sentences, front-loaded with the core action and no filler. It is efficient, though the second sentence ('canonical transaction data from the consensus layer') is largely a restatement of the first.

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 read-only lookup with no output schema, the description compensates by naming what is returned and noting the proof is optional. The remaining gap is routing context against the many sibling transaction tools, which the description does not address.

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%, so both parameters are already documented in the schema, including the 'without 0x prefix' constraint and the prove flag. The description only restates 'by its hash' and 'optional proof of inclusion,' adding no format or default detail beyond the schema.

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 description gives a specific verb and resource ('Returns a transaction by its hash') and enumerates the payload (tx result, height, optional proof), so the purpose is unambiguous. However, in a namespace that also exposes get_cosmos_tx, get_tx, get_tx_details, and search_cometbft_tx, it never states how it differs from those siblings, so sibling differentiation is only weakly implied by 'from the consensus layer.'

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 when-to-use, when-not-to-use, or alternative-selection guidance. With this many overlapping transaction tools available, the agent is left to guess why it should call get_cometbft_tx rather than get_cosmos_tx or search_cometbft_tx.

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