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

Beyond the readOnly/openWorld-false annotations it discloses that no wallet, chain, market, bank or counterparty lookup occurs and that no money moves, plus the paid URL (0.10 USDC on Base via x402 exact), the 10 free signed-wallet calls per rolling 30 days, and the Ed25519 signed receipt. It also specifies the X-Wever-Wallet-Proof binding requirement, which is exactly the kind of auth precondition annotations cannot express.

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 description is dense but front-loaded: purpose, then output semantics, then sourcing constraint, then verdict vocabulary, then transport and payment facts. Every sentence carries information, though the payment/contract/human-page tail could be tightened without losing meaning.

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, and the description compensates by describing the report contents (ranked verdict, fee_mismatch_found, not_comparable) and the signed receipt. For a paid, multi-quote comparison tool it covers sourcing, cost, auth and failure vocabulary fully enough to invoke 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 already 100%, so the baseline is 3; the description adds meaning by explaining how the inputs are used downstream — quotes are ranked by effective rate, stated fees are reconciled against amounts and rate, and expiry is judged against as_of. It does not elaborate on edge-case formats (units, string vs numeric amounts), but the computational role of each field is made clear.

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 opens with a specific verb and resource ("submit two or more conversion quotes") and enumerates the exact inputs and outputs the signed report computes: effective rate, ranking, spread percentage, fee reconciliation and expiry flags. It also names the two live-pricing siblings it is not, so an agent can distinguish it from wever_market-data-check and wever_fair-value-brief without opening a 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?

It states the operative constraint clearly ("Supplied quotes only") and routes market-data and fair-value work to named alternatives. It stops short of addressing other overlapping comparison siblings such as wever_quote-compare or wever_escrow-quote, so the exclusion set is incomplete, but the core when/when-not split is explicit.

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