dw_product_field_delete

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

No annotations provided. Description discloses irreversibility and single-category constraint, key behavioral traits for a delete operation. Could mention return value or permissions, but adequate.

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 states action and irreversibility, second gives usage constraint. No wasted words, 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?

Covers essential aspects: action, irreversibility, usage constraint. No output schema, but not needed for delete. Adequate for its complexity.

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 100%, both parameters described. Description adds value by explaining cross-category usage and enforcing sameness constraint, beyond schema.

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 product fields from a single category', specifying action and resource. Constraint 'Irreversible' adds clarity. Distinguishes from siblings like dw_field_delete and dw_product_category_delete.

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?

Provides explicit constraint: 'All ids must belong to the same categoryId' and guidance for multiple categories: 'call this tool once per category'. No explicit alternatives but clear context.

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