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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces rather than contradicts this by stating it reads only the material in the call, with no network request, fetch, money movement, message, sharing, or external write. It goes well beyond annotations by disclosing cost (0.10 USDC per call on Base via x402 exact), the 10 free signed-wallet calls per rolling 30 days, the required X-Wever-Wallet-Proof binding to the exact JSON arguments and route, and that the response carries an Ed25519 signed receipt.

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 content is useful but delivered as long run-on sentences with several distinct concerns (input shape, verdict logic, HTTP route, pricing, auth binding, receipt, contract links) chained together. Key facts such as the verdict values and the payment model are not front-loaded. It is over-full for a two-parameter tool and could be tightened without losing information.

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?

There is no output schema, so the description carries the burden of describing the return, and it does: a report with an Ed25519 signed receipt and one of three verdicts. It also covers pricing, authentication binding, the API route, and links to the contract and human page. The only gap is that it does not describe the report's internal structure beyond the verdict and receipt.

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 the baseline would be 3. The description nevertheless adds real meaning: each metric needs what it measures, its value, how it is computed, and what it excludes, and it enumerates the measures (transaction count, settled value, payer count, average ticket) that map to the enum. It also names the substantive checks applied, such as self-payment and test-payment exclusion and distinct-wallet payer counting, which tells the agent how to populate the fields well.

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 states a concrete verb and resource: submit a payments activity report / metrics definition for a quality check, and names the three possible verdicts (inflatable, quality_unverified, commerce_backed). It also routes one adjacent case to the sibling wever_settled-value-check. The core purpose is clear, but it is buried in a dense paragraph about what the report must contain rather than stated up front.

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?

Usage is implied: submit headline payment numbers with definitions when you need an accountability verdict, and ticket-size metrics summaries belong to wever_settled-value-check. There is no explicit 'use this when / do not use this when' framing and no statement of prerequisites beyond the payment/auth mechanics. The routing hint to a sibling is present but partial.

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