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

Annotations already cover safety (readOnly=true, destructive=false, idempotent=false), and the description adds real context beyond them: 404 behavior for pending/unknown hashes, no charge on failures, and that each successful call costs $0.01 with the first 25 free. It does not describe response shape beyond the field list or pagination, but for a single-object lookup that is minor.

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, then routing, input format, edge case, and pricing. Dense but nearly every clause carries decision-relevant information; the pricing/free-tier clause at the end is slightly packed together with the read-only statement, costing a point on flow.

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 naming the fields returned. Combined with the 404 behavior, pricing, and read-only guarantee, an agent has everything needed to decide, call, and interpret the result.

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% with one required parameter, so the baseline is 3; the description earns above that by restating the 0x-prefixed 64-hex constraint in context and supplying a concrete valid hash example, plus the 404 consequence for a hash that isn't found. Marginal addition over schema, but useful for validation.

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 HyperEVM, eth_getTransactionReceipt) and enumerates the exact return fields: success/reverted status, gas used, effective gas price, fee in HYPE, log count, contract created. It explicitly separates itself from hyperevm_tx, so an agent can choose 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 when-to-use ("confirm a payment or call went through") and names the alternative for the complementary case ("for sender, value and calldata use hyperevm_tx"). It also covers the edge case of a pending or unknown hash returning 404 uncharged, removing the main ambiguity an agent would hit.

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