delete_category

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

With no annotations, the description fully discloses behavioral traits: permanent deletion, irreversibility, product disassociation without deletion, and potential subcategory association impact. It also describes the return structure, making the tool's behavior transparent.

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 well-structured with sections for purpose, API, return, and side effects. It is concise but includes some redundant details like the exact API endpoint. Still, it front-loads the key information effectively.

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, the description covers purpose, usage, side effects, and return structure comprehensively. It omits error cases or permission requirements but is otherwise complete given the tool's simplicity and lack of output schema.

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 a single parameter described. The description adds no further meaning beyond the schema's 'category ID' context. Baseline 3 is appropriate as the schema already carries the burden.

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 clearly states it deletes a product category permanently. It specifies the resource (category) and action (delete), and distinguishes from siblings like update_category and create_category by focusing on removal. The [WRITE] prefix and side effects reinforce the destructive nature.

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?

It states it is suitable for removing disabled or incorrectly created categories, providing clear context. However, it does not explicitly mention when not to use it or compare with alternatives like update_category for deactivation. The side effects help guide appropriate usage.

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