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

With no annotations, the description carries the full burden and does disclose the non-obvious commercial detail: no x402 challenge, free to call directly. It also gives an HTTP equivalent (GET), which signals a safe read. It stops short of stating idempotency, auth needs, or whether the payload is static versus versioned per request.

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 payload description is front-loaded, and the payment note is separated out usefully. The inline dash-bullet formatting is slightly awkward, and 'every report is reproducible from them' is mildly promotional rather than operational, but overall there is little waste.

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?

No output schema and no annotations exist, so the description must explain what comes back — and it does at the level of content categories (input contract, graded fields, verdict states, corpus identity). It does not describe the response shape (envelope keys, format), which is the one remaining gap for a zero-parameter retrieval tool.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing the description could add that the empty schema does not already settle. It briefly restates the 'call directly' invocation pattern, which is consistent with 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?

Names a concrete resource — the published criteria for the Receipt Verification service (settlement-evidence/v1, receipt form) — and enumerates its contents (input contract, graded fields, verdict states, pinned test corpus identity). This lets an agent distinguish it from receipt_verify/receipt_precheck, though it never names those siblings explicitly to sharpen the boundary.

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?

"Read these before paying" gives an implied ordering cue relative to the verification flow, but the description never states the alternative tool that actually performs verification or precheck. An agent must infer from the name alone that receipt_verify is the downstream call this criteria document supports.

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