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

With no annotations, the description carries the load and does disclose the key traits: the underlying RPC call (implying a read), the exact payload contents, that logs are returned raw rather than decoded, and a per-call price in USDC. It omits behavior for edge cases such as a pending or unknown hash, and doesn't state whether the hash is checked across chain defaults.

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?

Front-loaded with the purpose and return fields, then the alternative and price — a sensible order with no filler. The telegraphic comma-list style is dense but readable; nothing is redundant.

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 2-parameter tool with no output schema, the description covers what it returns, how to call it, what the alternative is, and what it costs. The only residual gap is chain defaulting, which is minor against an otherwise self-sufficient definition.

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 description coverage is 0%, so the description has to compensate. The example {hash:"0x…", chain:"base"} usefully signals that hash is a 0x-prefixed hex string and chain is a human-readable chain name, but it never says whether chain is optional, what it defaults to, or which chains are supported.

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 via eth_getTransactionReceipt") and enumerates exactly what comes back: status, gas used, effective gas price, fee, contract created, log count plus raw logs. That enumeration also separates it from sibling tools like tx_status and chain_events, which return different shapes.

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?

"Use /tx ($0.003) for decoded transfers + confirmations" gives an explicit alternative and the condition that selects it, plus the price delta ($0.002 vs $0.003) as a tiebreaker. The gap is that it names an endpoint path rather than the sibling tool name tx_status, so the agent must map one to the other.

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