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

With no annotations, the description carries the full burden. It usefully discloses the return payload shape and a pricing/access constraint ('5 free trial calls per signed wallet'), which implies a paid, wallet-authenticated read. It omits which chain(s) are supported, whether pending/unmined transactions are handled, and any rate or auth specifics.

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?

One front-loaded sentence plus a short trial-limit note; nothing is wasted and the core purpose leads. The emoji and pricing tag are minor noise but do not impede comprehension.

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?

The description compensates for the absent output schema by naming returned fields, but with no annotations, three fully undocumented parameters, and no chain/network context, it is not complete enough for an agent to invoke this confidently among a dense field of transaction-related siblings.

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% across three parameters (tx, hash, input), and the description adds nothing about them. Critically, it never clarifies that these appear to be alternative ways to identify the same transaction, which is exactly the kind of ambiguity the description should resolve.

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 ('Looks up a transaction receipt') and enumerates the returned fields (status, block number, gas used, sender), so the agent knows exactly what it gets. It does not, however, distinguish itself from close siblings such as x402-tx-decode, x402-tx-explain, or x402-block-explorer, which all touch transaction data.

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?

There is no when-to-use guidance and no mention of alternatives. The description also never says which input to supply (tx vs hash vs input) or under what conditions this tool is preferable to the sibling decoders/explainers, leaving the agent to guess.

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