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

Annotations only declare readOnlyHint and idempotentHint=false; the description adds real behavioral color by disclosing that the response covers consensus/finalized heights and whether the vault was updated or the transaction reverted. It does not explain why the operation is non-idempotent (e.g., heights advancing as the tx finalizes), which is the one gap.

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 return contents and closed with the usage cue; no filler. The field enumeration is long but each item earns its place by telling the agent what it can extract.

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 compensates reasonably by listing the key returned fields. It lacks sibling routing and any note on when results stabilize (relevant given idempotentHint=false), but for a single-required-param read tool it is close to sufficient.

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?

One parameter with 100% schema description coverage, so the schema already carries the meaning ('transaction hash (inbound or outbound)'). The description adds nothing about format or validation, so baseline 3 applies.

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 ('Returns comprehensive transaction details') and enumerates the payload contents (observed txs, actions, outbound txs, heights, vault updated vs. reverted). It is clear what the tool does, but it never distinguishes itself from close siblings like get_tx, get_tx_status, get_tx_stages, or get_cometbft_tx.

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?

'Use this for deep transaction analysis' implies a context but names no alternatives and gives no exclusion criteria. An agent facing get_tx, get_tx_status and get_tx_stages alongside this tool has no explicit routing rule for when the deep variant is warranted.

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