delete_product

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

The description lacks any disclosure of behavioral traits beyond the literal delete action, such as whether deletion is permanent, cascading, or requires specific authorization. Without annotations, the description carries full burden and fails to provide this critical 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?

The description is concise with one sentence, but it is under-specified. While front-loaded, it sacrifices essential details for brevity, making it minimally acceptable.

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?

Given the simplicity of a delete operation with two required parameters, the description should at least mention effects (e.g., permanent deletion, no undo) or return value. The absence of this information, combined with no output schema, leaves the agent without necessary context.

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 100% with clear parameter descriptions (workspace_id: 'Workspace slug or UUID', id: 'Product UUID'). The tool description adds no additional meaning beyond the schema, so a 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 description 'Delete a product' is a clear, specific verb+resource pair that precisely indicates the tool's action. It effectively distinguishes this tool from siblings like create_product, update_product, and list_products.

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?

No guidelines are provided on when to use this tool, prerequisites, or alternatives. The description offers no context about required permissions, dependencies, or situations where deletion might be disallowed.

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