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

Beyond the readOnly/openWorld/destructive annotations, the description states the operation reads only the submitted material with no network request, fetch, money movement, message, sharing, configuration change or external write. It also discloses cost and access mechanics (0.10 USDC per call on Base via x402 exact, 10 signed-wallet free calls per rolling 30 days), the required X-Wever-Wallet-Proof binding to the exact JSON arguments and route, the signed Ed25519 receipt, and the possible verdict values.

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 core instruction is front-loaded in the opening sentence and every clause carries substantive information (verdicts, pricing, auth binding, contract link). It is dense to the point of being run-on inside parentheses, and the endpoint/contract/human-page boilerplate could be compressed, but no sentence is 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?

For a nested two-object input with no output schema, the description covers the important ground: what to submit, what the report asserts, the enumerated verdict set, the receipt signature, and the paid-access mechanism. It does not describe the report's internal structure beyond the verdict and findings, which is the main residual gap.

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?

With 67% schema coverage and nested objects, the description adds real meaning by explaining what a flow entry must carry: each step's words, the credentials/accounts/approvals it asks for, and the step where payment happens, which maps onto step, text, requires and payment. The optional label is not mentioned, and the listing object's fields are only lightly characterized, 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 first sentence names a specific verb and resource: submit one tool/service listing plus its ordered purchase flow, and the report's function is stated concretely (does an agent learn every credential requirement before the payment step). It explicitly routes a closely related concern (listing decidability) to the sibling wever_catalog-listing-check, so an agent can separate the two without opening either 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 clearly framed: this tool is for credential-requirement timing relative to payment, and the alternative for listing decidability is named with wever_catalog-listing-check. What is missing is an explicit when-not-to-use boundary (e.g. what to do when only the listing text exists and no flow is available), but the routing context is otherwise strong.

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