delete_category

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

The description discloses the default failure mode (HTTP 422 with structured dependents payload), the force=true behavior, and irreversibility. The destructiveHint annotation is true, and the description aligns with it, adding valuable context about what happens with dependencies.

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?

Three sentences with no waste. The default behavior is front-loaded, the force option is explained, and the irreversibility warning is included. Every sentence earns its place.

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 destructive tool with no output schema, the description covers the key decision point (force flag), the failure mode, and the consequence. It doesn't describe the success response format, but that's less critical for a delete operation. The description is complete enough for an agent to call it correctly.

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%, so the schema already documents both parameters. The description adds context about force=true's irreversibility and the default failure behavior, but doesn't add much beyond the schema's parameter descriptions. Baseline 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 the tool deletes a single category or category group, distinguishing it from sibling tools like delete_tag or delete_transaction. It also specifies the key behavior of failing by default when dependencies exist, which differentiates it from a simple delete.

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 explains when to use force=true vs default behavior, which is essential usage guidance. It doesn't explicitly name alternative tools for deleting other resources, but the context of category deletion is clear and the force flag guidance is strong.

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