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

With no annotations provided, the description carries the full burden and does well: it declares read-only behavior, no keys and no signing, a public RPC dependency, and a bounded block window. It does not disclose rate limits or what happens if the block range is too wide, so a mutation-free safety profile is clear but operational limits are only partially covered.

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?

Three short sentences, front-loaded with the 'Read-only:' safety signal and the core action. The trailing 'No keys, no signing' largely restates read-only, which is mild redundancy, but nothing else is wasted.

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?

For a read-only fetch tool with no output schema and only 33% parameter coverage, the description supplies the essentials — safety posture, RPC source, block bounds, and downstream compatibility with reconcile_payouts. It could state the recipient cap and range defaults to be fully self-sufficient, but an agent has enough 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 only 33%, so the description must compensate, and it adds meaning for the key inputs: recipients, the optional single payer ('from'), and the block window. Network and token are self-evident from their enums, but it omits the 50-recipient cap and the 5000-block default range that the schema mentions, leaving a small gap.

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 ('look up public USDC/USDT Transfer events to the given recipients') with the scope (optionally one payer, up to 10000 recent blocks, public RPC). It also names the downstream sibling (reconcile_payouts), so an agent can place it in the workflow without opening a schema.

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?

The description gives clear context for use — read-only lookup whose 'output plugs straight into reconcile_payouts' — which frames it as the discovery step before reconciliation. It stops short of an explicit when/when-not rule or naming a sibling to prefer instead, but no sibling overlaps this data-fetching role, so the guidance is adequate.

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