Resume product sales across channels

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

Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true (external side effects), but the description adds no behavioral context—it doesn't warn about irreversible changes, approval token requirements, or the difference between preview (dry run) and execute. It merely restates the action without disclosing side effects.

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 a single, front-loaded sentence that efficiently conveys the core action. No wasted words or redundant details.

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?

Despite having an output schema, the tool has a complex command object with multiple required parameters, a dual preview/execute mode, and external side effects. This one-sentence description does not explain the workflow, approval process, or how it differs from other lifecycle operations, making it insufficient for correct invocation.

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%, and the description only clarifies the 'channels' parameter ('every selected channel'). Critical parameters like sku, confirm, idempotency_key, and approval_token are not explained, so the description does not compensate for the schema's lack of detail.

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 specifies a clear verb+resource+scope: 'Preview or resume a product on every selected channel.' It distinguishes from siblings like product_stop and product_publish by focusing on the 'resume' action, which is a distinct lifecycle operation.

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 implies usage is for resuming a paused product on selected channels, but does not explicitly state when to use it versus alternatives like product_publish or product_stop, nor any exclusions. Context from the name/title suggests the intended scenario, but explicit guidance is missing.

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