wave_delete_product

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

The description hints at soft deletion via 'archive', but doesn't clarify whether the action is reversible, what data is affected (e.g., invoices referencing the product), or required permissions. No annotations are provided to fill this gap.

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?

Exactly one sentence, no wasted words. The key action and outcome are conveyed efficiently. Suitable for a simple deletion operation.

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 deletion tool without output schema or annotations, the description is too minimal. It lacks information about side effects, reversibility, authorization, and whether the archive is permanent. Given the complexity of business data (products tied to invoices), this is insufficient.

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%, so the baseline is 3. The description adds no extra meaning beyond the schema: productId and businessId are described only by their names and types. No hints about default behavior, required context, or relationship between parameters.

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 a specific verb ('Delete') and resource ('a product or service'), and includes 'archive' in parentheses to indicate soft deletion. It clearly distinguishes from sibling tools like wave_create_product, wave_list_products, and wave_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?

No guidance on when to use this tool versus alternatives (e.g., wave_update_product for product adjustments, or wave_create_product for new items). No conditions, prerequisites, or post-effects are mentioned, leaving ambiguity about appropriate use.

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