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

Beyond the annotations, the description discloses the payment model (0.10 USDC per call on Base via x402, 10 signed-wallet free calls per rolling 30 days), the authentication requirement (bind X-Wever-Wallet-Proof to the exact JSON arguments and route), the side-effect boundary (no page fetch, no account access, no counterparty contact, no money movement), and the output shape (report with an Ed25519 signed receipt, verdict in consistent/mismatches_found/elements_missing). This is exactly the kind of context annotations cannot carry.

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 and input mode are front-loaded, and the long middle sentence on what gets checked is dense but earns its space by defining the verdict. A few trailing items (contract path, human page URL, x402 mechanics) sit in the middle of the block rather than being grouped, so the reading order is slightly cluttered.

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?

For a nested six-parameter tool with no output schema, the description covers inputs, checking semantics, verdict vocabulary, return artifact (Ed25519 signed receipt), cost, and auth binding. An agent has everything needed to construct a correct call and interpret the result.

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% and every nested field is documented in the schema, so the schema does the heavy lifting and baseline 3 applies. The description enumerates the instruction fields and policy dimensions, which helps orientation, but adds no format or precedence detail beyond what the schema already states (e.g. 'A field takes precedence over the text').

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 payment instruction as fields, text, or both — and spells out the checking scope (internal consistency plus comparison against an optional invoice and payer policy). An agent can tell what the tool produces. It stops short of naming which sibling it replaces (e.g. wever_invoice-payment-match or wever_payment-policy-check), which is where a 5 would live.

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 context is implied well: supply fields and/or text, optionally attach an invoice or policy, and get a verdict. The description also clarifies it reads only call material, which bounds the use case. But there is no explicit 'use this when X, use the sibling when Y' guidance despite a crowded namespace of adjacent payment and invoice checks.

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