delete_category

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

Annotations mark it as destructive. The description adds crucial details: default failure with structured 'dependents' payload, force delete is irreversible, and disassociation from related entities. No contradictions.

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 concise sentences. First states the primary action, then the two behavioral modes. No redundant information.

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?

Given two simple parameters, no output schema, and the destructive annotation, the description covers all necessary points: action, default behavior, force behavior, and irreversibility. It's complete for the tool's complexity.

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 already covers both parameters with descriptions. The description enriches 'force' by explaining its effect (disassociate from related budgets, transactions, etc.), adding value beyond the 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?

The description specifies the exact action ('Delete a single category or category group') and distinguishes between two modes (default fails with dependencies, force=true deletes). This clearly differentiates it from sibling tools like delete_tag or delete_manual_account.

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 the default behavior (fails if dependencies) and when to use force=true (to delete despite dependencies). It does not explicitly compare to alternatives but provides clear usage context.

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