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

Far exceeds the annotations: it discloses the paid URL, price (0.10 USDC per call via x402 exact), the shared 10 free calls over rolling 30 days, that billing is separate from wallet visibility, and that X-Wever-Wallet-Proof must bind to the exact JSON arguments and this path rather than /mcp. It also enumerates what the tool cannot do (sign, submit, transfer, spend), which the readOnlyHint alone does not spell out.

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?

Purpose is front-loaded and there is no filler, but the description is long for a 4-parameter read tool, and the billing/auth-header material is dense enough to compete with the core read semantics. Every sentence is relevant, but the density could be tightened.

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 no output schema, the description names the returned fields (amounts, timestamps, transaction hashes) and points to /api/treasury-contract for schemas, coverage and billing terms, which covers the main gaps. Minor incompleteness remains around result volume/pagination given limit defaults to 20.

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 75% and the description reinforces the key detail: wallet_address must use the exact EIP-55 checksum. It also characterizes limit and the UTC time window as bounding the returned history, adding meaning beyond the raw Schema types.

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?

Opens with a specific verb+resource+scope: 'Read recent native USDC transfers into and out of a wallet on Base mainnet,' including the fields returned. This clearly separates it from the sibling wever_treasury-balance (which reads balances, not 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?

It gives concrete constraints on usage (optional limit/time window, EIP-55 checksum requirement, directing the agent to /api/treasury-contract and the 402 body for schemas and terms). However, it never explicitly states when to prefer this tool over the sibling treasury tools, leaving selection to inference.

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