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

No annotations exist, so the description carries the full burden. It does add genuinely non-schema behavior: the chain is Base and each call costs 0.001 USDC via x402 — valuable cost/venue disclosure. It omits error behavior for unknown hashes, handling of reorgs, and whether 'pending' results are polled or cached.

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?

Two sentences, zero padding, with what the tool returns front-loaded before the usage hint and the pricing note. Every clause contributes something an agent can act on.

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 and no annotations, the description steps in to enumerate the return payload, the chain, and the payment model, which is most of what an agent needs for a single-parameter lookup. Only edge-case behavior (unknown hash, reorg, pending semantics) is left uncovered.

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% and there is a single required parameter, so the schema already carries the contract, and the schema's only description is a zero-hash example. The description adds modest meaning by specifying the hash is a transaction hash rather than a block hash, but nothing on format or 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?

Names a specific verb+resource (transaction status for a given hash), pins the chain (Base), and enumerates the returned fields (status, block number, confirmations, gas used). It stops short of explicitly differentiating itself from close siblings like evm_tx and evm_receipt, which overlap heavily with 'status'.

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 it to check whether a transfer confirmed' gives one concrete scenario, but there is no when-not guidance and no mention of the obvious alternatives (evm_tx for full transaction detail, evm_receipt for logs/events). The agent must infer the boundary itself.

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