delete_product

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

The description discloses the important behavior that products with existing orders are soft-deleted, adding context beyond the tool name. However, it does not clarify what happens to products without existing orders, leaving ambiguity about potential permanent deletion.

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 short sentences with the main action front-loaded and the necessary caveat in the second sentence. Every word is purposeful with no redundancy.

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 one-parameter tool, the description covers the core outcome and a key behavioral nuance. The ambiguity about no-order products and lack of return/error details are minor gaps given the tool's simplicity.

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 input schema already fully describes the single 'id' parameter as 'Product ID to deactivate' (100% coverage), so the description adds no additional parameter information. Baseline 3 is appropriate.

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 the specific verb 'Deactivate' and names the resource 'product from your store', with the added nuance of soft-delete behavior. This clearly distinguishes it from sibling tools like update_product and create_product.

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 for deactivating a product, which is a clear context. However, it does not explicitly mention alternatives or when not to use it, relying on the tool name and sibling context.

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