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

Beyond annotations, the description discloses detailed side effects: running Coinbase's validator, per-check fixes, firing indexing settlement from its own funded wallet, pointing to self-settle above a threshold, confirming the merchant-feed entry, idempotency, concurrent double-spend protection, and human escalation after 5 failures. This is rich behavioral context that annotations alone do not provide.

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 dense but purposeful; the first sentence establishes the core purpose, and subsequent sentences unpack the pipeline steps, safety guarantees, and escalation behavior. Every sentence adds value, though the single-paragraph format could benefit from bullet points for easier parsing.

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?

This is a complex multi-step tool with an output schema, and the description covers the full lifecycle: validation, settlement logic, self-settle fallback, feed confirmation, receipt return, idempotency, and failure escalation. It is sufficiently complete for an agent to invoke it safely and understand expected behavior.

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 input schema already provides 100% coverage of the single parameter listing_key, including its format and requirement. The description references the key but adds no additional semantic meaning beyond what the schema states, so the baseline 3 is appropriate.

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 clearly identifies the tool as a resumable pipeline driver for a purchased Bazaar Listing Package, stating its role in advancing through validation, settlement, and feed confirmation. It is distinct from sibling tools like create_bazaar_listing and validate_x402_endpoint, which serve different stages.

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 description states to use it any time with the listing_key for a purchased package, providing clear context and implying it is the ongoing driver after purchase. It does not explicitly name alternatives or exclusions, but the specific mention of 'purchased package' and 'resumable pipeline driver' differentiates it from creation/validation tools.

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