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

Annotations only flag readOnly/openWorld and idempotentHint=false; the description explains WHY repeats are not free (per-call charge, so repeats are not free) and confirms read-only semantics ('changes nothing'). It adds pricing, free-tier, and 404-on-pending behavior — context no annotation carries.

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?

Purpose and return fields are front-loaded in the first sentence, alternatives follow, then input format, then billing. The billing/pricing tail is dense and slightly run-on, but each clause (404 uncharged, failed calls free, repeats not free) carries decision-relevant information.

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?

No output schema exists, and the description compensates by enumerating the return fields an agent would need (status, gas used, gas price, fee, log count, created contract). Combined with input format, error behavior and cost model, an agent has everything needed 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% and already documents the single hash parameter, so the baseline is 3. The description goes slightly beyond by repeating the 0x/64-hex format and supplying a concrete valid example hash, but adds no new semantic constraint.

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 ('Transaction receipt on Unichain') and enumerates the returned fields (status, gas used, effective gas price, fee in ETH, log count, contract created). It explicitly differentiates itself from the nearest sibling by pointing to unichain_tx for sender, value and calldata.

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?

Gives a concrete when-to-use ('confirm a payment or call went through') and names the alternative plus the condition that selects it ('for sender, value and calldata use unichain_tx'). It also states the failure case (pending/unknown hash returns 404, uncharged), leaving nothing to inference.

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