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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context: the time window is only the last ~48h, the result includes aggregate counts/volumes and sample hashes, and the tool is preflighted so the caller won't be charged during an RPC outage. There is no contradiction with 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 compact and front-loaded: it opens with the core counterparty-check purpose and follows with scope, output summary, and a cost-safety note. Every sentence earns its place and there is no padding or redundancy.

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 only one parameter, a full output schema, and annotations covering read-only/idempotent behavior, the description covers the network, asset, time window, transfer directions, and output contents. The preflighted payment-safety note is a meaningful addition, and nothing needed to actually invoke this tool correctly is missing.

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 fully documents the single address parameter with 100% coverage, so the baseline applies. The description adds context by clarifying that the address is the participant in sent/received USDC transfers on Base, but it does not add format or constraint details 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 names a specific function: an on-chain counterparty check of USDC transfers SENT and RECEIVED by an address over the last ~48h of Base blocks. It also specifies the output contents (counts, volumes, sample tx hashes), which clearly distinguishes it from siblings like balance_check and tx_activity.

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 intended use is reasonably clear from the 'counterparty proof' title and the transfer-direction framing, but there is no explicit statement about when to choose this tool over alternatives such as tx_activity or balance_check. No when-not-to-use conditions or exclusion criteria are provided, so usage guidance is implied rather than explicit.

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