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

Well beyond the readOnly/openWorld annotations, the description discloses that each call is paid (0.10 USDC via x402 exact on Base), that a shared quota of 10 signed-wallet free calls per rolling 30 days applies, that X-Wever-Wallet-Proof must be bound to the exact JSON arguments and route, and that a report with an Ed25519 signed receipt comes back. It also names the data source (public Base USDC Transfer logs and balances) and the transport (POST /api/wallet-statement), so cost and auth behavior are transparent before invocation.

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 and scope are front-loaded in the first two sentences, and the later sentences (payment, proof binding, receipt, contract link) each carry distinct operational information. It is dense and slightly cluttered with boilerplate links and jargon like 'expense close pack', which keeps it off a 5.

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 carries the return-shape burden and does so thoroughly: totals in/out, net change, transfer counts, up to 10 largest transfers with dates and counterparties, and opening/closing balances with the caveat about where readers establish them. Cost, auth binding, transport and receipt verification are all covered, leaving nothing essential for a correct call.

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 description coverage is 100%, so both parameters are already documented, including the YYYY-MM pattern and EIP-55 handling. The description restates month range and the address form parity with wever_wallet-activity-brief but adds no new syntax or edge-case semantics, so the baseline 3 holds.

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: a monthly USDC statement for one Base address, framed as an expense close pack. It distinguishes itself from the sibling wever_wallet-activity-brief by naming that tool as the underlying reader and by enumerating what the statement adds (statement lines, signed receipt), so an agent can tell the two apart without opening either schema.

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 use case (monthly expense close, accountant-ready output) and the accepted input window (current month to date or one of the twelve before) are stated, which implicitly routes raw-activity needs to wever_wallet-activity-brief. However, there is no explicit when-not clause or named alternative for agents that just want transaction-level activity data; that exclusion is left to inference.

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