Recent USDC payments to an address

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

No annotations provided, so description carries full burden. Clearly states it is a read-only operation (returns transfers) and specifies scope (last N blocks, Base mainnet). Does not disclose potential limitations like pagination or rate limits, but for a simple query tool, adequately transparent.

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: first states core functionality, second provides usage context. No redundant or unnecessary information. Well-structured and front-loaded.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description provides the essential purpose and context. Lacks details about return format or ordering, but this is acceptable for a straightforward query tool with clear sibling differentiation.

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 descriptions for both parameters. Description adds minimal value by rephrasing blocks_back as 'over the last N blocks', but essentially repeats schema. Baseline 3 due to high schema coverage.

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?

Description clearly states it returns USDC transfers TO a given address over the last N blocks on Base mainnet. Specifically identifies as a convenience wrapper for x402 merchants, distinguishing it from siblings like usdc_balance or recent_transfers.

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?

Describes the target use case (x402 merchants verifying incoming agent payments), giving clear context. Does not explicitly state when not to use or list alternatives, but the specificity provides good guidance.

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