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 several behaviorally important facts: the price ($0.02 USDC on Solana), that the result is a signed grade, and that grading is per-field with two verdict levels. It does not say whether the call is pure computation or requires a funded wallet/x402 handshake, nor what happens on malformed payloads, so it is informative but not complete.

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?

A single sentence that front-loads the cost and then states exactly what the payment buys. No filler, no restatement of the name, and the two verdict values are given inline.

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 tool with a nested payload object and no output schema, the description covers the return semantics (COMPLETE/INCOMPLETE, field-by-field, signed) and the payment model. The main omission is the meaning of 'op' and of 'facilitator', but since there is no output schema to lean on, the description is otherwise reasonably self-contained.

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 67%: payload and facilitator are documented in the schema, but the 'op' parameter has no description and no enum. The description never mentions 'op' despite pricing 'per op', so it does not compensate for that gap or explain which op values are valid. Baseline 3 applies since the schema does most of the work.

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 names a concrete operation: producing a signed completeness grade of a captured payment payload, checking resource + extensions.bazaar field by field and returning COMPLETE / INCOMPLETE. That is specific enough for an agent to know what it gets back. It stops short of differentiating itself from close siblings such as listing_check_check, listing_check_precheck, or listing_check_promise, which an agent cannot disambiguate from this text alone.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no reference to the four sibling listing_check_* tools. The only implicit signal is that it costs $0.02 per call, which hints at a final verification step, but the agent must infer that.

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