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

Beyond the annotations it discloses a great deal: the call is self-contained (no page fetch, no account access, no merchant contact, no money movement), consistent with openWorldHint=false; the paid URL cost of 0.10 USDC per call on Base via x402 exact with 10 signed-wallet free calls per rolling 30 days; and the requirement to bind X-Wever-Wallet-Proof to the exact JSON arguments and route. It also bounds interpretation ('matches words, figures, dates and named items... does not interpret meaning beyond that matching') and states the return carries an Ed25519 signed receipt, plus pointers to the contract and human page.

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 purpose is front-loaded, but the body is a dense run of comma-spliced clauses mixing reconciliation semantics, route, payment/auth mechanics, legal contract link, and a human page URL. Every element is individually relevant, yet the packing makes key operational facts (x402 price, wallet-proof binding) hard to scan. Some structural separation would raise the score.

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 burden of describing returns and does so: report structure by category, expected amount and cent-level difference, Ed25519 signed receipt. Payment, auth binding, and interpretation limits are all covered. The main gaps are error/failure behavior and how partial or unmatched input is reported beyond the two named buckets.

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 already 100%, so the baseline is 3, but the description adds real semantics: matching is by label, percentage fees need a base amount (mapping to base_amount), and currency/rate mismatches are reported with the expected amount and cent-level difference. It does not explain the format auto-detection, the charges_label/schedule_label recording, or the 200/500 item caps, so it stops short of full 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?

The description names a concrete verb and resource pair: submit a fee schedule plus a quote/invoice and get a signed reconciliation report pairing each charge to its schedule fee by label. The scope ('lists the charges the schedule does not list and the listed fees charged at a different amount, rate or currency, with the expected amount and the difference to the cent') makes the operation unmistakably a fee-vs-charge reconciliation, distinct from generic invoice or pricing siblings. It falls short of 5 only because no sibling tool (e.g. wever_invoice-check, wever_pricing-evidence-check) is named to route the agent explicitly.

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 by the scenario ('submit a fee schedule and a quote or invoice') but there is no explicit when-to-use/when-not-to-use statement and no named alternative among the many evidence-check siblings. The 'reads only the material in the call' sentence functions as a constraint rather than selection guidance. An agent can infer the context, but must compare sibling descriptions itself.

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