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

Annotations already mark the call read-only, idempotent, and non-destructive, and the description adds the state it can return (success/reverted, gas, fee, logs, deployed address) and how the API behaves when no receipt exists. It also discloses pricing and authentication requirements, going well beyond the structured hints.

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?

The description is front-loaded with a memorable summary and then gives dense but relevant detail on returned fields, edge behavior, and access requirements. It is slightly long because of pricing/header details, but no sentence is 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 one required parameter, a full output schema, and rich annotation hints, the description still adds the critical missing-receipt interpretation and contract-deployment behavior. There is no obvious information an agent needs to call it correctly.

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%: the only parameter, hash, is described as 'Transaction hash'. The description merely repeats that hash is required and does not add format or source guidance beyond the schema, so the schema carries the semantic burden.

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 identifies a specific resource (Base transaction receipt) and the core question it answers: success/reverted, cost, and touched contracts. It is distinct from sibling transaction tools by focusing on the receipt and even covers contract-deployment output, so an agent can tell it apart from base_tx or tx_decode.

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?

Clear context is provided: supply a hash to get execution results, and interpret a missing receipt as pending/dropped/never rather than failure. It does not name an alternative tool like base_tx for when receipt fields are not needed, so it stops short of explicit exclusions/alternatives.

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