delete_attribute

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds critical behavioral context beyond that: it deletes all attribute terms and removes the attribute from all products. This cascading effect is exactly the kind of disclosure that helps an agent avoid unintended data loss.

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?

One sentence conveys the full destructive scope without unnecessary words. It's front-loaded with the core purpose and immediately adds the high-stakes side effects.

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?

The description is sufficient for a destructive delete operation, covering the most important side effects (terms, product associations). It doesn't describe return values, but no output schema exists and return values are less critical for a delete tool. Omitting the 'force' requirement is acceptable since the schema documents it.

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 covers 100% of parameters (id, force, fields) with descriptions for each. The tool description adds no extra parameter information, but given the complete schema coverage, a baseline 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?

Description clearly states the action ('Delete'), the resource ('global product attribute'), and the full scope ('all its terms' and 'removes the attribute from all products'). This distinguishes it from sibling tools like delete_attribute_term or delete_category.

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?

Implied usage is clear: use when you want to delete an entire global attribute including its terms and product associations. It doesn't explicitly say 'when not to use' or name alternatives, but the sibling set (delete_attribute_term, delete_category) makes the distinction sufficiently obvious.

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