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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the receipt is for a *mined* transaction and enumerates what the result contains, including L2 L1 fee and decoded Transfer/Approval events. It says nothing about what happens for a pending or unknown hash, chain-specific caveats, or auth/rate limits.

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, with the purpose front-loaded before the use case. The return-field enumeration is dense but each item conveys real information.

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?

An output schema exists, so the description need not explain return values (though it does, redundantly but harmlessly). Given zero annotations and zero schema parameter descriptions, the definition is under-specified for a two-parameter tool: chain selection and hash format are left entirely to inference.

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 0%, so both parameters are undocumented in the schema. The description gives no meaning to `hash` (format, tx vs block hash) and never mentions the `chain` parameter or its default of ethereum, which is a meaningful omission for an EVM tool spanning chains. It fails to compensate for the coverage gap.

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?

Names a specific resource (receipt of a mined EVM transaction) and enumerates the returned fields: success/revert, gas used, effective gas price, fees, created contract, decoded logs. An agent knows exactly what it gets back. It does not, however, differentiate itself from close siblings such as evm_transaction_status or event_logs.

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 to confirm a payment or swap" gives one concrete scenario, so usage is implied rather than spelled out. There is no guidance on when to prefer evm_transaction_status or event_logs instead, and no exclusion criteria (e.g. pending/unmined transactions).

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