delete_category

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

The description goes beyond the destructiveHint annotation by clarifying that products are not deleted but become uncategorized. This is a valuable non-obvious side effect. It does not mention the soft-delete versus permanent-delete nuance, but the schema already documents the 'force' parameter, so the description's disclosure is 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?

The description is two concise sentences. It immediately states the core action, then adds the essential caveat. No wasted words or redundant padding, making it easy to parse.

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 annotations and a well-described schema, the description captures the most critical contextual detail: products become uncategorized. It does not explain return values or mention soft-delete behavior, but those are not essential for this tool's primary usage, and the schema covers the force parameter.

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?

All three parameters (id, force, fields) are fully described in the schema, providing 100% coverage. The description itself adds no parameter-specific information, so per the rubric the baseline score 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?

The description opens with the specific verb-resource pair 'Delete a product category', clearly stating the tool's purpose. It also distinguishes from sibling delete tools by adding the key clarification that products within the category are not deleted but become uncategorized, which resolves any ambiguity about cascading deletion.

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 provides clear context for when to use the tool by stating the action and its immediate consequence. However, it does not explicitly mention alternatives or when not to use it (e.g., using delete_product to remove category products first), so it stops short of full usage guidance.

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