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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond that: the $0.001 USDC cost per call, the supported chains, and that it is byte-identical to a specific GET endpoint. This is meaningful behavioral disclosure without contradicting the annotations.

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 the core value proposition, then adds cost, chain support, and an exact endpoint equivalence. It is slightly dense but each sentence earns its place and there is 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?

For a simple two-parameter read tool with a full output schema and safety annotations, the description is complete. It covers purpose, cost, supported chains, and exact API equivalence, so an agent has everything needed to select and invoke 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%, so the schema already documents both required parameters. The description does not add much parameter-level meaning beyond the example hash in the byte-identical URL, which mostly duplicates the schema's format guidance.

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 clearly states the tool returns a transaction plus its receipt in one call, with confirmations, block, status, gas used, and revert reason. It explicitly contrasts this with 'two paid reads and a race,' distinguishing it from separate tx and receipt tools like chain_tx and chain_receipt.

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 description gives clear usage context: use this after sending a transaction when you need both the transaction and its receipt together. It implies the alternative is making two separate reads, though it does not name sibling tools explicitly or state when not to use it.

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