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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds the cost ($0.005 USDC via x402), which is useful operational context. However, it does not disclose limits, pagination, ordering, or which block range defaults to 'recent', leaving important behavioral ambiguity.

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?

Two concise sentences with the primary action first, filtering option second, and cost last. Zero filler; every clause earns its place.

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 query with 5 parameters and no output schema, the description is adequate but leaves gaps: no mention of return format, pagination, block-range defaults, or how multiple filters combine. The 'recent' qualifier is vague and could mislead an agent about the query window.

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 all parameters are already documented with descriptions. The description adds only the concept of filtering by 'from or to a specific wallet', which maps to to_address/from_address, but adds no new semantic detail beyond the schema.

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 states the tool finds ERC-20 transfers on Base and optionally filters by sender or recipient wallet. It distinguishes the resource (ERC-20 transfer events) from siblings like base_erc20_balance or base_logs, though it does not name them.

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?

No explicit guidance on when to use this tool versus alternatives like base_logs or base_transaction. The implied use case is clear (need transfer events), but there are no conditions, exclusions, or alternative recommendations.

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