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

Goes well past the annotations: pricing model ($0.01/call, first 25 free, failed calls free), 404 responses being uncharged, and an explicit note that repeats are not free — which reconciles the seemingly odd idempotentHint=false with a purely read-only operation. The "reads or computes only and changes nothing" line confirms destructiveHint=false without contradicting it.

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?

Dense but front-loaded: purpose and return fields first, then routing to base_tx, then input format, then cost. The closing sentences repeat the read-only/charging points already implied earlier, which is mild redundancy but the length is defensible for a paid, error-prone call.

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 the description compensates by naming every returned field, including reverted-vs-success and contract creation. Error behavior, cost, and the read-only guarantee are all covered, leaving nothing an agent needs before calling.

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 hash format is already documented; the description restates the 0x-prefixed 64-hex constraint and adds a concrete example value, plus the behavior of a pending/unknown hash. That is useful but largely duplicative of the schema, so it sits just above baseline.

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 ("Transaction receipt on Base (eth_getTransactionReceipt)") and enumerates the returned fields: status, gas used, effective gas price, fee in ETH, log count, contract created. It explicitly distinguishes itself from base_tx ("for sender, value and calldata use base_tx"), so the agent can separate the two without opening either schema.

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 trigger ("Use to confirm a payment or call went through") and names the alternative for the other need (base_tx). It also covers the edge case of a pending or unknown hash returning 404, which is exactly the failure mode an agent would otherwise misread as an error.

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