Delete category

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

Explicitly states 'This is destructive and cannot be undone', which is critical behavioral information. Also includes the HTTP endpoint pattern. No annotations provided, so description carries full transparency burden.

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?

Two concise sentences with no fluff. Front-loaded with action and resource, then adds critical behavioral note.

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 operation with one parameter, the description covers action, resource, and irreversibility. However, it omits possible response or error info, but that is acceptable given typical delete tool conventions.

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 parameter 'id' described as 'The category id.' The description adds little beyond the schema; 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?

The description clearly states 'Delete a category by id', specifying the action and resource. It distinguishes from sibling tools (e.g., delete_customer, delete_item) by focusing on 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?

The description implies use when you need to delete a category, but provides no guidance on when not to use it or prerequisites. Sibling tools differentiate by entity, but no explicit usage context.

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