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

With no annotations, the description carries the full burden; it usefully discloses the paid cost ($0.008) and the main returned fields (from, to, value, gas used, status, block info). It says nothing about behavior for unknown/pending hashes or error cases, leaving meaningful gaps for a paid call.

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 compact sentences with no filler, and the return-field list is informative. Leading with the price is slightly unconventional but still front-loads a key decision factor.

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 single-parameter read tool with no output schema, the description covers cost and return fields, but omits not-found/pending behavior and the distinction from chain_tx_receipt, leaving an agent without enough to invoke confidently in edge cases.

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?

The single hash parameter has 100% schema description coverage ('0x-prefixed 64-hex transaction hash'), so the schema does the heavy lifting. The description only restates 'by hash' and adds no format or constraint detail beyond it, matching the baseline 3.

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 (get) and resource (Ethereum transaction details by hash), so the agent knows exactly what it fetches. However, it never distinguishes itself from the close sibling chain_tx_receipt, which an agent could easily confuse with this tool.

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?

The phrase 'by hash' implies the required input but gives no guidance on when to prefer this over chain_tx_receipt, nor any prerequisites or exclusions. The agent must infer the choice between overlapping sibling tools.

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