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

With no annotations, the description carries the full burden. It discloses the return fields, the payment model ('you only pay for successful reads: invalid input, not-found and upstream errors cancel settlement'), and the cost ($0.002 USDC on Base). It does not cover rate limits or explicitly state read-only status, leaving some behavioral gaps.

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 description is two sentences, front-loaded with the core purpose and followed by a precise use case and payment terms. Every sentence earns its place with no waste.

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?

Given no output schema, the description lists the key return fields (status, confirmations, block time, from/to, value, fee) and explains the payment model. It is nearly complete, though it could clarify the paymentSignature parameter's role and any authentication requirements.

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%, so the schema already documents all three parameters fully. The description adds only marginal context by mentioning '7 EVM chains' and specific chains, which is already in the schema; it does not add meaning beyond what the schema provides.

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?

The description names a specific verb and resource (transaction status) and enumerates the returned fields (pending/success/reverted, confirmations, block time, from/to, value, all-in fee) across 7 EVM chains. It does not explicitly differentiate itself from sibling chain_* tools, so it stops short of a 5.

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?

It states a clear use case: 'Use it to confirm a payment or deployment landed.' However, it does not mention when not to use it or name any alternative sibling tool, so it lacks exclusions.

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