delete_tag

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

Annotations already declare destructiveHint=true, but the description adds valuable context beyond that: 'Does NOT affect products that had this tag; they simply lose the tag association.' This discloses a non-obvious side effect (no cascading deletion), which is helpful. It does not mention irreversibility, but the 'force' parameter in the schema covers permanent deletion.

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?

The description is one well-structured sentence with an explanatory clause. It is front-loaded with the action and contains no redundant filler.

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 tool with complete schema coverage and a destructiveHint annotation, the description provides the essential purpose and a key behavioral side effect. It doesn't mention return values, but no output schema exists and the schema covers the request parameters, making this sufficiently complete for a tool of this 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 description coverage is 100%, with all three parameters (id, force, fields) individually documented. The description adds no new parameter-level meaning, so the baseline of 3 applies.

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 begins with 'Delete a product tag,' a specific verb and resource that clearly distinguishes it from sibling tools like delete_category and delete_brand. It also clarifies the scope by specifying 'product tag.'

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 clearly implies the tool's use case (deleting a tag) but provides no explicit guidance on when to use it versus alternatives, such as updating a product to remove a tag association without deleting the tag. Context is clear but exclusions/alternatives are absent.

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