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

The annotations already mark this as a read-only operation, and the description consistently adds that it returns observed transaction data, status, and processing stages. It does not add deeper behavioral context such as auth requirements, rate limits, or why idempotentHint is false, but it does provide some useful return-shape information beyond the annotations.

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 description is a single front-loaded sentence that states the operation and the main return categories with no wasted wording. It is appropriately sized for a simple get-by-hash tool.

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?

Input schema and annotations are clear, and the description broadly covers return contents. However, given the large family of overlapping transaction-related sibling tools and no output schema, the description does not provide enough differentiation for an agent to know when this specific tool is the right choice.

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?

There is only one parameter, and the schema description already defines it fully as the transaction hash, including inbound or outbound. The tool description adds no syntax, format, or semantic detail beyond the schema, so the baseline of 3 applies when schema coverage is effectively complete.

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 states a clear verb and resource: returns transaction details for a given hash, including observed data, status, and processing stages. However, it does not distinguish this tool from siblings such as get_tx_details, get_tx_stages, get_tx_status, get_cometbft_tx, or get_cosmos_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?

There is no guidance on when to use this tool instead of related sibling tools that also retrieve transaction information. The description gives no exclusions, prerequisites, or alternative-selection criteria.

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