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

With no annotations, the description carries the full burden and delivers: success/reverted semantics, block time, confirmations, fee split into L2 gas and L1 data fee, decoding capped at the first 25 transfers, and 404-without-charge for unknown or unmined hashes. It also discloses cost and payment rail (x402, USDC on Base/Solana), which an agent needs before calling.

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 trigger, then Input/Output/Edge/Example/Price in telegraphic form; nearly every clause carries information. It is slightly dense and the pricing sentence is a separate concern, but nothing is redundant filler.

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, so the description must describe return values and it does so in detail, including the decoded ERC-20 transfer cap and error behavior. Combined with the pricing note, an agent has everything needed to call and interpret this single-parameter tool.

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% with a single required parameter, so the baseline is 3 and the schema does the heavy lifting. The description adds value beyond it by restating the input shape, supplying a concrete example hash and query-string usage, and reinforcing the 404/not-charged behavior on unmined or unknown hashes.

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 (confirm a Base transaction/payment) plus the exact facts returned: success/reverted, payer/payee, token and amount. This cleanly separates it from siblings like base_token_flows or base_wallet_balances, which cover aggregate flows or balances rather than a single transaction's 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?

Opens with an explicit trigger condition ('Use when an agent must confirm a Base transaction or payment landed'), which is clear usage context. It does not name a sibling alternative or state when-not to use it (e.g. versus base_token_flows for multi-transfer history), so it stops short of a full routing guide.

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