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

Annotations only declare readOnlyHint=true; the description adds meaningful behavior beyond that: the two-step payment handshake, the fact that a null return means the node does not know the hash, and that the raw node shape is passed through. That is real unannotated context, though it omits retry/expiry semantics for the payment.

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 purpose is front-loaded and the payment protocol is clearly sequenced, but the full pretty-printed measured output blob is large and largely redundant with the plain statement that the raw transaction is returned. It earns some value as a return-shape sample but is heavier than needed.

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 embedded measured-output sample usefully conveys the return shape, and the payment flow is spelled out. It is close to complete for a single-parameter read, missing only failure/expiry behavior for the signed payment retry.

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% for the single `hash` parameter, and the description's '0x + 64 hex' restatement duplicates the schema. Baseline 3 is appropriate since the schema already carries the semantics.

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 ('on-chain read: a transaction by its hash') and pins the network to Ethereum mainnet, which is exactly the distinction that separates it from base_eth_gettransactionbyhash and eth_mainnet_eth_gettransactionbyhash in the sibling list.

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 description gives strong invocation guidance (call once unpaid to get terms, retry with a signed payment at _meta["x402/payment"]), but never states when to choose this tool over sibling reads or the base/eth_reads variants. Usage context is implied rather than stated as selection criteria.

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