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

Goes well beyond the readOnly/idempotent/openWorld annotations: it discloses the price ($0.002 per call), the HTTP endpoint (GET /evm/tx), that invalid input is rejected before any charge, that input is truncated to the first 1 KB, and how a P0 bearer key changes behavior (the tool makes the paid call itself and deducts the price). Minor deduction because the two response modes – 'returns the exact paid x402 request' vs 'call that URL … to get the data' vs the keyed mode returning data directly – are worded densely enough that an agent could misread which it will receive.

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?

The purpose and the evm_receipt disambiguation are front-loaded well, but the middle is a run-on sentence chaining price, endpoint, schema link and client instructions, and the payment-mode explanation is split awkwardly across the paragraph. Every fact is arguably useful, yet the payment logistics could be compressed or moved to a trailing clause.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, and for a paid open-world tool it covers auth (bearer key, where to buy one) and billing. The remaining gap is the ambiguity about whether a plain call returns data or merely a payable URL, which matters for a tool whose whole point is a paid fetch.

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 100% and both parameters (hash pattern, chain enum with base default) are already fully documented, so the baseline is 3. The description adds the chain roster and the 1 KB input truncation, but nothing about the hash format or chain selection semantics beyond the schema.

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 ('a transaction by hash') plus the exact return contents (from, to, value, nonce, gas/fee fields, block, confirmations, method id, input) and the supported chains. It also explicitly distinguishes itself from the sibling evm_receipt, so an agent can pick correctly 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?

Opens with an explicit trigger ('Use when you need a transaction by hash'), and names the alternative with its selecting condition: 'to know whether it succeeded (status, gas used, logs) use evm_receipt'. The payment path options (x402/MPP client vs P0 access key) are also spelled out as a decision the caller must make.

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