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

Annotations already cover read-only, idempotent, and non-destructive behavior, lowering the bar for additional disclosure. The description adds meaningful context beyond annotations: data comes from Covalent, results are limited to 'recent' transfers, calls cost $0.03 over x402 on Base, and no wallet or API key is required. There is no contradiction with the annotations.

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 fairly compact and front-loaded, but it repeats the same idea in 'A wallet's in/out transfers of a token' and 'Recent transfers of a specific token for a wallet.' It also restates 'Required inputs: address, token,' which duplicates the schema. The pricing and auth details are useful, but some redundancy keeps it from being maximally concise.

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 simple two-parameter read-only tool with an output schema available, the description is largely complete: it covers inputs, returned fields, provider, recency, pricing, and access requirements. It does not specify pagination limits or exact time windows, but 'recent transfers' and the existing output schema make this sufficient for an agent to call the tool 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?

The input schema already documents both parameters with 100% descriptive coverage, so the baseline of 3 applies. The description merely repeats 'address, token' as required inputs without adding format details, constraints, or chain/network semantics. It does not need to compensate for schema gaps.

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 clearly identifies the tool as returning a wallet's recent in/out transfers of a specific token and enumerates the returned fields: direction, amount, USD value, counterparty, tx hash, and time. It lacks a direct imperative verb like 'lists' or 'returns,' and it does not explicitly contrast with sibling 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?

The description gives a clear intended use case: 'For agents tracking token flows and cost basis.' It also communicates access requirements such as pricing, prepaid header, free-call allowance, and no wallet/API key needed. It does not mention exclusions or name alternative tools, but the usage context is explicit enough.

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