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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the pay-per-call cost ($0.002), that invalid input is rejected before charging, that input is truncated at 1 KB, and that supplying a P0 bearer key makes the tool perform the paid call itself with a deduction. Those are non-obvious cost, validation and auth behaviors an agent must know.

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 'Use when' trigger and ending with the sibling exclusion, so the key selection cues are at the edges. It is a dense single block covering two invocation modes and payment plumbing, which is a lot of prose for two parameters, though most sentences carry real 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, but the description enumerates the returned fields, notes the response includes a schema and example, and explains the dual direct/paid-URL invocation paths plus the error-before-charge guarantee. An agent has everything needed to call it 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% — the hash pattern and the five-value chain enum with default 'base' are fully documented in the schema. The description restates the chain list but adds no format or semantics beyond it; the 1 KB note concerns returned input data, not a parameter. Baseline 3 applies.

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 concrete verb and resource (fetch a transaction by hash) and enumerates exactly what comes back: from, to, value, nonce, gas/fee fields, block, confirmations, method id and truncated input. It explicitly names the sibling evm_receipt as the tool for status/logs, so it is distinguishable from related tools without opening a 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?

"Use when you need a transaction by hash on Base, Ethereum, Arbitrum, Polygon or Optimism" gives the triggering condition, and the closing sentence routes the agent to evm_receipt when success status, gas used or logs are wanted. Both the use case and the alternative are explicit.

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