delete_project_category

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

The description discloses a key behavioral side effect: issues using the category are left without one unless reassigned to another category. This goes beyond the schema and annotations (none provided), adding important context about the consequences of deletion. It does not mention permissions or reversibility, but the main behavioral trait is covered.

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 concise and well-organized: opening with the purpose, then the behavioral note, and a clearly formatted args section. Every sentence provides value, and there is no redundancy or clutter.

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 deletion tool with two parameters and an output schema, the description covers the essential contextual details: what happens to issues using the category and the meaning of both parameters. Minor gaps such as authorization requirements exist, but the tool's simplicity and the presence of an output schema make the description sufficiently complete for an AI agent to select and use 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?

Despite having 0% schema description coverage, the description fully explains both parameters: category_id identifies the category to delete, and reassign_to_id specifies a replacement category to receive orphaned issues, with 0 meaning none. This adds meaningful semantics beyond the bare schema names and types.

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's action with a specific verb and resource: 'Delete an issue category.' This unambiguously distinguishes it from sibling tools like list_project_categories, create_project_category, and update_project_category, and the behavior is described.

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 provides clear context for when to use the tool: when an issue category needs to be deleted, with optional reassignment of orphaned issues. It doesn't explicitly compare to alternatives, but the purpose is self-evident and the side effects are explained. However, it does not explicitly state when NOT to use it or mention alternatives.

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