Publish one product to multiple channels

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

The description complements annotations by disclosing parallel execution and the preview vs. create modes, which are not captured by readOnlyHint, openWorldHint, etc. It does not detail failure handling or approval requirements, but the annotations already cover the basic safety profile.

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, concise sentence that directly states the core functionality. It is front-loaded and contains no filler.

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 with many parameters (idempotency_key, approval_token, payloads, dry_run) and an output schema, but the description is minimal. It fails to explain the preview/execute workflow, how channels are chosen, what 'in parallel' means for error handling, or what the response will contain.

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 does not compensate for the complex command object. It hints at 'preview or create' (matching the confirm parameter) but provides no clarification for idempotency_key, approval_token, payloads, or channel selection semantics.

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 states it 'previews or creates one master product across all selected channels in parallel,' identifying the exact action and resource. It distinguishes the tool from siblings like product_update or product_stop by focusing on multi-channel publishing.

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 provides clear context that this is for publishing a product across multiple channels, with a preview/execute dichotomy. However, it does not explicitly mention when to avoid this tool or recommend alternatives like product_update for edits, so it lacks exclusions.

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