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

Adds considerable context beyond annotations: 404 on pending/unknown hashes with no charge, failed calls free, and per-call pricing via x402/credits. This is consistent with readOnlyHint=true and idempotentHint=false ('each call is charged, so repeats are not free'). It does not disclose rate limits or response shape beyond field names, so it falls just short of the top mark.

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 and return contents, then the routing hint, then the input spec, then pricing. Dense but mostly earning its place; the pricing/credits sentence is the longest and slightly heavy for a tool description, though it is the only place that info appears.

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?

No output schema exists, yet the description enumerates the meaningful return fields (status, gas used, effective gas price, fee in ETH, log count, created contract). Combined with error behavior, pricing and input format, an agent has everything needed to call it correctly and interpret the result.

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%, so the baseline is 3; the description earns extra credit by restating the 0x-prefixed 64-hex format, supplying a concrete example hash, and defining what a pending/unknown hash does. It goes beyond the schema's one-line parameter doc without adding validation details.

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+resource ('Transaction receipt on Ethereum (eth_getTransactionReceipt)') and enumerates the returned fields, then explicitly contrasts with the sibling eth_tx for sender/value/calldata. An agent can distinguish it from arb_receipt/base_receipt etc. only by chain naming, but within the eth_ family it is unambiguous.

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 an explicit use case ('confirm a payment or call went through') and names the alternative tool with the condition that selects it ('for sender, value and calldata use eth_tx'). Also states the failure mode for pending/unknown hashes, so nothing about when-to-use is left implicit.

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