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

With no annotations, the description carries the full burden and does meaningful work: it discloses the output fields, the chain (Base), and an explicit per-call cost of 0.002 USDC over x402, which is a real behavioral constraint an agent must budget for. It stops short of describing error behavior for hashes that are not yet mined or do not exist.

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 sentences, no filler, front-loaded with what is returned before the usage hint and the price. Slightly dense enumeration of fields, but every clause earns its place.

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?

Covers return contents, chain, cost, and a usage cue for a one-parameter read tool with no output schema, which is close to sufficient. The notable remaining gap is the lack of any stated behavior for reverted/pending/not-found hashes and no pointer to the overlapping siblings.

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?

One required parameter at 100% schema coverage, so the schema already documents the hash and even supplies an example. The description adds nothing about the hash beyond what the schema provides; baseline 3 applies.

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 pairing: it returns a transaction receipt on Base with an enumerated set of fields (status, block, gas used, effective gas price, log count, created contract). That is well beyond the name. It does not, however, distinguish itself from the sibling evm_tx_status, which the agent will see alongside it.

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?

"Use it to confirm a transaction or read its status" gives a usable context, but it is exactly the usage that the sibling evm_tx_status implies, and the description never says when to prefer one over the other or what happens for a pending/unknown hash.

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