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

With no annotations, the description carries the full behavioral burden. It usefully enumerates the returned data (status, gas used, event logs) and implies a read-only RPC lookup, but says nothing about behavior for unmined/unknown hashes, error handling, rate limits, or auth requirements.

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?

A single front-loaded sentence that names the resource, the RPC method, and the returned fields with no filler. 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?

There is no output schema and no annotations, so the description is the only source of truth. It lists the receipt contents, which helps, but omits the nested 'payload' input shape and the failure mode for unmined or unknown transactions, leaving gaps for a tool whose structured fields are silent.

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 0% and the single parameter is a nested payload.hash object, so the schema alone does not explain it. The description compensates partially by naming eth_getTransactionReceipt, which tells the agent the hash is a transaction hash, but it never mentions the 'payload' wrapper or confirms the hash format.

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 verb+resource ('Transaction receipt'), the underlying RPC call (eth_getTransactionReceipt), and the chain scope (Base mainnet), so it is clearly distinguishable from siblings like base_tx or base_block. It stops short of explicitly contrasting itself with base_tx, but the receipt-vs-transaction distinction is implicit in the wording.

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?

The phrase 'for a mined Base mainnet transaction' gives an implicit precondition (the transaction must already be mined, so pending txs will not yield a receipt), but there is no explicit when-to-use, when-not-to-use, or named alternative such as base_tx for pending transactions.

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