Delete Category

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

Annotations already indicate destructive and idempotent behavior. The description adds valuable context: assignments are moved to the default None category, and the response returns the deleted Category ID. This goes beyond the annotations, though it repeats the permanence warning.

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 somewhat repetitive, stating 'cannot be undone' twice and 'permanently removes' twice. It could be more concise by removing redundancy. The information is front-loaded but contains unnecessary repetition.

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 the simple tool with 3 parameters, annotations, and no output schema, the description covers the main effect, side effect on assignments, response format, and module context. It lacks details on subcategory handling, but overall it is fairly 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 coverage is 100% with clear descriptions for all 3 parameters (company_id, project_id, category_id). The description only lists required parameters and mentions the endpoint format, adding no new semantic information 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 clearly states 'Delete a Category from a Project' with specific verb and resource. It explains side effects (assignments moved to default None category) and response format (returns deleted Category ID). This distinguishes it from sibling tools like delete_subcategory or update_category_name.

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 when to use the tool (to permanently delete Resource Planning records) but does not explicitly contrast with alternatives like delete_subcategory or update_category_name. It includes a warning that the action cannot be undone, but no guidance on when not to use it.

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