delete_product

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

The description discloses irreversibility, a key behavioral trait. However, with no annotations provided, it fails to mention potential side effects on related data (e.g., orders, memberships), authorization needs, or whether the operation is synchronous.

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 extremely concise with two short sentences, front-loading the main action. Every word is essential and no extraneous information is present.

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 tool with one parameter and no output schema, the description covers the key action and irreversibility. However, it lacks mention of prerequisites or post-conditions, leaving gaps for an AI agent unfamiliar with the system.

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 100%, with product_id described as 'The product ID to delete.' The description adds no extra semantic value beyond the schema's own description, so baseline score of 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 verb 'Delete' and resource 'product' are explicitly stated, making the action unmistakable. It clearly distinguishes from sibling tools like create_product and update_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 notes the action is irreversible, implying caution, but does not specify when to use this tool versus alternatives (e.g., when a product should be removed from catalog vs. deactivated). No prerequisites or context for safe usage.

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