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

Beyond the annotations (readOnly, non-destructive, closed-world), the description discloses the kind of work performed ('matches words, figures, dates and named items ... does not interpret meaning beyond that matching'), the name-normalization rule (legal suffixes set aside, AWS treated as Amazon Web Services), and that the result carries an Ed25519 signed receipt. The payment path (0.10 USDC per call on Base via x402 exact, shared 10 signed-wallet free calls per rolling 30 days) and the X-Wever-Wallet-Proof binding requirement are material operational facts an agent must know before calling. Nothing contradicts the annotations; the only minor gap is that it does not say what happens on wallet-proof mismatch.

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?

It is front-loaded with the action and the report contents before the operational metadata, and every sentence is substantive. The single dense paragraph mixes purpose, payment, wallet binding, and links, which makes it harder to scan than a short structured layout, but there is little outright filler.

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, yet the description fully characterizes the report (paired processors, missing/added/changed entries with quotes) and the signed receipt, so an agent knows what comes back. Given the five-parameter, offline text-matching design, the added notes on payment, proofs, and matching limits leave nothing an agent needs in order to call it correctly.

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 is 3; the description earns an extra point because it explains the matching semantics applied to the name fields ('legal suffixes set aside, AWS and Amazon Web Services as one'), which the schema cannot express. It still largely restates the accepted claim shapes already documented in 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 verb and resource ('submit subprocessor claims ... and the agreement or subprocessor list') and states the deliverable precisely: a report pairing processors by name and listing missing, added, and changed entries with quotes. That is enough for an agent to tell it apart from sibling evidence checks such as wever_certification-evidence-check or wever_data-evidence-check without opening any 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?

Usage is implied through the scoping statement 'Reads only the material in the call: no page fetch, no account access, no merchant contact and no money movement', which tells the agent this is an offline text-matching check needing fully supplied inputs. However, no sibling tool is named as an alternative and there is no explicit when-to-use / when-not-to-use routing, so the agent must infer the choice among the many *-evidence-check siblings.

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