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

Annotations already cover read-only and destructive hints, but the description adds real value: per-call pricing model ($0.01, first 25 free, failed calls free) and the crucial caveat that repeats are billed, which explains the idempotentHint=false annotation. It also discloses the 400 rejection for malformed addresses as uncharged.

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 core purpose is front-loaded and the description is dense with useful detail, but the charging information is partially repeated ("first 25 free; failed calls free" then "each call is charged, so repeats are not free") and the inline example address occupies space that could be trimmed.

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 compensates by naming the returned fields (direction, counterparty, amount, transaction) and ordering/cap (newest first, up to 50). Error behavior, cost, and the read-only guarantee are all covered, so an agent has everything needed to call it correctly.

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%, so the schema already documents the token default (USDC), the 1-2000 block range and the default of 1000. The description mostly restates those facts, adding only a worked address example; baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a specific verb ("List"), a precise resource ("recent transfers of one ERC-20 token ... on Gnosis"), and scope qualifiers (in and out, last N blocks, newest first, up to 50). It is immediately distinguishable from sibling tools like gnosis_token_balance and from the same tool on other networks.

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 the concrete use cases ("confirm a payment arrived or see what was sent") and explicitly routes the balance use case to gnosis_token_balance. The malformed-address/400 note tells the agent what input conditions fail.

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