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

readOnlyHint=true already covers the safety profile, but the description adds real context beyond annotations: the return contents (status, block, gas used, logs) and the non-obvious two-call payment protocol. It does not state rate limits or error behavior, but for a simple read this is strong supplementary disclosure.

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?

Front-loads the purpose well, but repeats essentially the same content three times ('transaction receipt...', 'via eth_getTransactionReceipt', 'Returns the node's receipt...') and says 'Ethereum mainnet' redundantly. The payment instructions are useful but the receipt description is not tight.

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 does the required work of naming what the receipt contains and explaining the payment flow, so an agent has enough to invoke it correctly. Minor gap: no mention of failure modes (e.g., pending/missing transactions).

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 description coverage is 100%, so the single hash parameter is fully documented. The description merely restates the '0x + 64 hex' format already present in the schema and adds no new semantic meaning, making the baseline 3 correct.

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: reads an Ethereum mainnet transaction receipt by hash, and enumerates the returned fields (status, gas used, logs). It is clearly distinct from the sibling eth_gettransactionbyhash (which returns the transaction, not the receipt), though it never names that sibling to make the distinction explicit.

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?

Gives a concrete operational flow for the x402 payment handshake (call once unpaid to get terms, retry with the signed payment at _meta['x402/payment']), which is valuable. However, it offers no guidance on when to choose this tool over the sibling transaction/block/log readers, so usage selection is left to inference.

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