dw_product_delete

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

Despite no annotations, the description discloses key behaviors: irreversibility and auto-formatting of IDs. However, it does not mention error handling, return values, or permission requirements, which would be helpful for a mutation tool.

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 sentences: first conveys purpose and irreversibility, second clarifies ID handling. No wasted words; essential information front-loaded.

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?

Adequate for a simple delete tool, but missing details on batch behavior, error responses, and whether deletion is synchronous. Given no output schema and no annotations, more context on usage outcomes would improve completeness.

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 50%, and the description adds significant meaning by explaining the required ID format and auto-formatting feature. This compensates for the schema's lack of description for languageId, though the languageId parameter is not explicitly detailed.

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 tool deletes one or more DynamicWeb products, emphasizing irreversibility and ID format. This distinguishes it from sibling tools like dw_product_get or dw_product_update.

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 use for deletion (irreversible) but does not explicitly specify when to use it versus alternatives like dw_product_update or dw_product_category_delete. No guidance on prerequisites or when not to use.

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