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

The description adds substantial behavioral context beyond annotations: the paid URL cost (0.10 USDC per call on Base), free-call allowance (10 signed-wallet calls over 30 rolling days), how to discover x402 terms via the backend 402 body, and that existing product credentials, signed mandates, and single-use action grants remain required. It also explicitly scopes authority ('grants no authority and never supplies server credentials') and clarifies that payment is only an API access fee, which explains why readOnlyHint=false despite the inspection framing.

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 long and front-loads pricing instead of the core inspection purpose, which appears only in the third sentence. It repeats authority boundaries across multiple clauses (e.g., 'grants no authority', 'never supplies server credentials', 'grants no spending authority') and includes vague filler such as 'This current money service follows its published inspection, policy evaluation or private invoice contract.'

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 7-required-parameter tool with no parameter descriptions and no output schema, the description provides strong operational and pricing context but leaves critical gaps: it does not explain how to supply authorization_nonce or min_confirmations, what 'mode' must be, or what the returned 'observed payment details' include. An agent could not reliably populate all required fields from this definition alone.

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 0%, so the description must carry all parameter meaning, but it only loosely maps a few fields: 'receipt reference' implies transaction_hash, 'recipient' implies payee, and 'amount' implies amount_atomic. It does not explain the required mode constant, payer semantics, authorization_nonce, min_confirmations thresholds, or the atomic-unit format constraints shown 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 contains a specific verb+resource statement: 'Inspect a canonical Base USDC transaction receipt for the configured Wever recipient and return the observed payment details.' This clearly distinguishes the tool's core operation from generic payment or receipt tools, though it does not explicitly name sibling alternatives such as wever_receipt-passport or wever_x402-payment-gateway.

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?

The 'Operating boundary' paragraph gives clear context for use: supply the receipt reference, then read chain, recipient, amount, and verification result. It explains that an agent links the receipt to its work record while a human inspects the same details. No explicit when-not conditions or named alternatives are provided, keeping it from a 5.

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