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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing billing behavior: no charge for an invalid hash, a hash not found on Base, or Base being unreachable, plus payment via x402 and a pointer to list_prices. The failure/billing exemptions are exactly the kind of operational detail an agent cannot get from structured fields.

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?

Front-loads the resource and lookup key, then the return-field inventory, then the billing caveats. The field enumeration in the opening sentence is long but justified because no output schema exists; otherwise the text is tight with no filler.

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 carries the return-value burden well by listing fields including the L1 data fee and decoded USDC transfers, and it covers cost and failure cases. It could say slightly more about what a pending transaction actually returns (e.g., whether confirmations/block are absent), which is the only notable gap.

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?

Only one parameter, and the schema already documents it fully (100% coverage) as a 0x 64-hex-character hash with a max length. The description adds nothing new about the parameter format, so the 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 and resource ('Base mainnet transaction lookup by hash') and then enumerates exactly what the response contains (status, block, confirmations, fees, USDC transfers). This clearly separates it from sibling chain_block, chain_balance, and chain_token, which operate on different resources.

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?

Provides a concrete use case ('confirming that a USDC or x402 payment really settled before delivering goods'), which tells the agent when to reach for it. It does not, however, explicitly exclude or route away from siblings such as chain_token or chain_block, so the agent must infer that distinction from resource names.

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