delete_product

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

With no annotations, the description carries the full burden. It discloses the destructive nature ('permanently delete') and adds a safety requirement (confirm user intent). This is more transparent than a generic 'delete' description, though it doesn't detail related data effects or error conditions.

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?

Two concise sentences with the most critical information front-loaded. Every word earns its place, and the reminder to confirm user intent is a valuable addition without unnecessary verbosity.

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?

For a simple delete operation with one parameter and an existing output schema, the description is complete. It notes permanence and a required safety step, which covers the main context an agent needs. No significant gaps are apparent.

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?

The schema has zero description coverage and only one required integer parameter. The description adds 'by ID' but does not explain the product_id semantics beyond what the parameter name and type imply. It's sufficient for a simple identifier, but the description could have explicitly stated that product_id is the identifier of the product to be deleted.

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 the action ('Permanently delete'), the resource ('one product'), and the scope ('by ID'). It distinguishes itself from sibling tools like create_product, update_product, and list_products by specifying deletion semantics and permanence.

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 includes a crucial usage guideline: 'Confirm user intent first,' which warns the agent to verify user intent before invoking this destructive action. It doesn't explicitly mention alternatives, but the purpose is clear enough that an agent would know when to use this over update_product or list_products.

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