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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries the useful burden and does: the tx is on-chain verified on Base, submission is idempotent per payment, and the side effect is seller reputation. Missing is what a false report costs the caller or whether reports can be retracted.

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 imperative trigger comes first and the supporting constraints follow, so an agent can act on the first clause alone. The closing sentence about honest sellers and flagging is motivational framing rather than operational detail and could be trimmed.

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 3-parameter, no-output-schema tool, the description covers the precondition, the evidence required, and the effect of the call. It does not describe what the tool returns on success versus on a rejected/duplicate tx, which is the main remaining 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?

Schema coverage is 100%, so the baseline is 3. The description adds real semantics the schema does not: the tx must correspond to an actual Base payment and is validated externally, and the once-per-payment rule tells the agent the tx acts as a dedupe key.

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?

Specific verb + resource: report whether a paid-for result was delivered, with the payment transaction as evidence. It clearly scopes itself to post-payment usage, though it never distinguishes itself from the similarly named sibling report_outcome, so an agent must infer the split.

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 trigger is explicit and front-loaded: 'CALL THIS AFTER PAYING a seller (x402 or any USDC payment on Base)'. It also states guardrails — real buyers only, once per payment — but names no alternative tool for the case where no payment occurred or the payment is disputed.

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