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

Despite annotations covering the safety profile, the description adds substantial operational context: the full status enum including not_found/unknown, the rule that an unknown hash is charged while a 5xx node error is not, latency (0.3-2s), price ($0.002), the shared 10-read free pool, and an untrusted-data warning. This is well beyond what readOnlyHint/idempotentHint convey.

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?

It is dense and front-loaded, leading with inputs and the return shape before pricing and safety notes. The long enumeration of return fields is a slight laundry list, but with no output schema each field 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?

With no output schema, the description fully compensates by enumerating return fields (status, block, fees, L1/blob splits, etc.) and the status semantics. Combined with pricing, latency, and security notes, nothing an agent needs to call it correctly is missing.

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% and both parameters are fully documented with pattern and enum, so the schema does the heavy lifting. The description restates the chain options and hash format but adds no format or edge-case detail beyond the schema, 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?

The description states a specific verb and resource ('read a transaction and its receipt on Ethereum or Base'), which cleanly separates it from adjacent siblings like get_block, decode_calldata, and decode_tx_logs. An agent knows exactly what this retrieves without opening the schema.

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?

Usage is implied by naming the supported chains (Ethereum, Base) and the accepted inputs, but the description never states when to prefer this over alternatives such as get_block or decode_tx_logs, nor any exclusions. Guidance is present but indirect.

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