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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the x402 payment model and the $0.003 USDC cost, which is genuinely behavioral context beyond the annotations, but says nothing about response shape, error cases, or what a failed/missing receipt looks like.

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 tight sentences, contents first and pricing second. The pricing sentence earns its place because it signals a paid (x402) call, though it could have been placed after explicit usage routing.

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?

For a single-parameter paid read tool with no output schema, the description covers what is returned and what it costs, which is the minimum an agent needs. It stops short of routing guidance versus siblings and of any note on the payment/x402 invocation flow.

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% and the single parameter `hash` is undocumented in both schema and description. The phrase 'transaction receipt' weakly implies this is a transaction hash, but no format, required-ness, or semantics are added beyond the regex pattern.

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 — a Base transaction receipt — and enumerates its contents (status, gas, decoded ERC-20 Transfer events). However, it never distinguishes itself from the adjacent base_tx sibling, leaving the agent to infer whether to fetch the receipt or the transaction.

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?

No when-to-use guidance and no named alternative. The agent is told what the tool returns but not when to prefer it over base_tx, base_transfers, or base_call, which is a real ambiguity given the sibling list.

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