Delete category

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false) by disclosing what actually happens to dependent data: posts are not deleted but reassigned to move_posts_to or the first other category. It also names the privilege requirement and the minimum-one-category guard, which is exactly the behavioral context an agent needs before a destructive call.

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?

Front-loaded with the action and its consequence in the first sentence, and the Settings/Categories/Delete analogy is compact. 'Admins only' is repeated verbatim in both the first and last sentence, which is the only wasted text.

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 three-parameter tool with no output schema but rich annotations, the description covers privilege, data-preservation behavior, fallback logic, and the blocking invariant. Nothing an agent needs in order to call it safely is missing.

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%, so the baseline is 3; the description adds the causal link between move_posts_to and the reassignment of posts, reinforcing why the parameter exists. It stops short of adding format detail beyond the schema's 'category_id from list_categories' hint.

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?

States a specific verb and resource ('Delete a feed category') plus the scope-affecting side effect ('move its posts to another'), which separates it cleanly from update_category, create_category, and delete_post in the sibling list.

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?

Gives concrete operating conditions: 'Admins only' and the invariant 'A group keeps at least one category', which tells the agent when this call will fail. It does not explicitly contrast with update_category or rename_level, so routing is implied rather than spelled out.

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