Resume product sales across channels

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

The description adds the preview/resume distinction, which implies different side effects (preview likely safe, resume mutates). However, it doesn't disclose the need for approval tokens, idempotency keys, or the cross-channel impact in detail. Annotations already indicate a non-read-only operation, but openWorldHint=true calls for more context.

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, front-loaded with the action, no filler. Every word adds value; it's concise and easily parsed.

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?

The tool is complex (nested command, two-phase approval, multi-channel, safety assertions), but the description provides only a high-level purpose. It doesn't explain the preview/execute workflow, how output schema reflects status, or the need for idempotency and approval. Sibling names and schema fields exist, but description fails to integrate them.

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 compensate. It vaguely hints at 'selected channel' and the preview/resume modes mapping to 'channels' and 'confirm'/'dry_run', but doesn't explain required fields like sku, idempotency_key, or approval_token, nor the safety assertions.

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 uses a specific verb ('Preview or resume') and names the resource ('a product') and scope ('every selected channel'), clearly distinguishing it from sibling tools like product_stop or product_publish. The title reinforces the action.

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?

No explicit guidance on when to use this tool versus alternatives like product_publish or product_update. It implies the resume use case but doesn't mention prerequisites, exclusions, or the difference between preview and execute modes.

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