product_delete

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

The description goes beyond annotations (destructiveHint=true) by explicitly stating 'IRREVERSIBLE' and that Voog does not retain deleted products. It also explains the force parameter's role and recommends proactive steps, providing valuable behavioral 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?

Three concise sentences that are front-loaded with the main action. Each sentence provides critical information without redundancy, making it efficient and easy to parse.

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 description covers all essential behavioral aspects for a destructive operation: irreversibility, required force parameter, and prerequisites. Although it omits return values or error handling, the core use case is sufficiently addressed.

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 coverage is only 33%, but the description adds meaning for the force parameter, stating it must be true for the deletion to proceed. It does not explain site or product_id beyond implying product_id is the id in the URL. This partially compensates for the low coverage.

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 'Delete a product' and includes the HTTP endpoint, making the action explicit. It distinguishes this from other sibling delete tools by emphasizing irreversibility and the need for force=true.

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 prerequisites: run products_list or product_get to confirm the id, and site_snapshot if the product might be needed later. It also warns that force=true is required, preventing accidental deletions. However, it does not explicitly mention when not to use this tool (e.g., for temporary deactivation).

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