Stop product sales across channels

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

Annotations already declare destructiveHint=true and readOnly=false. The description adds the 'Preview' option, indicating a non-destructive dry-run capability. But it does not explain the need for approval tokens, idempotency keys, or the permanence of the stop action beyond what annotations imply.

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 front-loads the core purpose ('Preview or stop a product') and the scope ('every selected channel'). No wasted words; it earns its place.

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 schema provides rich detail for parameters and an output schema covers return values. The description is minimal but sufficient to convey the core action, though it does not mention the safety workflow (preview before execute) or approval requirements. Given the available annotations and schema, this is adequate but could be more complete.

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 text provides no parameter-level details. While the schema has titles like 'Confirm' and 'Dry Run' that align with the description's 'Preview' phrase, the description does not compensate for the lack of parameter explanations, especially for security-related fields like approval_token and expected_external_ids.

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 ('stop') and resource ('product') with clear scope ('every selected channel'), and also mentions 'Preview' to indicate a dual mode. This clearly distinguishes it from siblings like product_resume and product_delete.

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: stop a product on selected channels, and mentions 'Preview' as a safer option. However, it does not explicitly state when to use this tool versus alternatives like product_delete or product_resume, nor does it mention prerequisites or exclusions.

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