delete_attribute_term

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

The annotation destructiveHint already signals that this is a destructive operation. Beyond that, the description discloses an important behavioral consequence: removing the term from all products using it. This adds meaningful context about the cascading effect, though it does not cover other aspects like permissions or reversibility.

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 two concise sentences, front-loaded with the main action and then the key side effect. No unnecessary words or filler, and it delivers clear information in minimal space.

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 delete tool with destructive annotation and complete parameter schema, the description covers the core purpose and a critical side effect. It doesn't specify return values, but no output schema is provided and this is typical for deletion tools. It is adequately complete given the simplicity of the operation.

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%, with descriptions for all four parameters. The tool description itself does not add further parameter semantics, but the schema already provides clear meaning (e.g., 'Term ID', 'Parent attribute ID'). Baseline 3 is appropriate since the description does not compensate or enhance 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?

Description states a specific verb ('Delete') and resource ('a value from a product attribute'), and further clarifies the scope ('Removes the term from all products using it'). This clearly distinguishes it from sibling tools like delete_attribute and delete_attribute_term.

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 when to use the tool (to delete a term from an attribute) but does not explicitly compare it to alternatives like delete_attribute or provide exclusions. It relies on the tool's name and context for differentiation, which is adequate but not fully explicit.

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