dw_product_category_delete

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

No annotations provided, so the description bears full burden. Discloses irreversibility and reveals the internal 3-step process (mark candidates, validate, delete), indicating partial failure behavior and validation steps. This goes beyond a simple delete description.

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?

Three sentences, each adding essential information: action, irreversibility+precondition, internal steps. No fluff, well-structured, and front-loaded with the core purpose.

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 delete operation with no output schema, the description covers purpose, irreversibility, precondition, and internal process. Could mention handling of partial invalid ids, but overall quite complete.

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% and includes example values for 'ids'. Description does not add extra semantic detail for the parameter beyond the schema. A 4 is appropriate as the schema already does the heavy lifting.

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?

Clearly states 'Delete one or more DynamicWeb product categories.' Specific verb+resource. Distinguishes from sibling tools like dw_product_category_save (create/update) and dw_product_category_list (list).

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?

Explicitly notes irreversibility and a critical precondition: fields must be deleted first via dw_product_field_delete, otherwise validation fails. Names the alternative tool, guiding the agent on prerequisites and dependencies.

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