deleteIssueCategory

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

The annotation readOnlyHint=false already signals a write operation, and the description 'Delete' is consistent with that. However, the description adds no behavioral details beyond the basic action — such as irreversibility, impact on dependent issue categories, or requirements for the reassign_to_id parameter. With annotations present, the description fails to add any value on top of them.

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 a single short sentence, so it is concise, but it is under-specified. It contains only the bare action and resource, offering no structural breakdown or additional context. It does not earn its place because it provides no information beyond the tool name, making it effectively unnecessary.

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 operation (delete) with two required parameters that are undocumented, the description is completely inadequate. There is no output schema to fall back on, and the description fails to explain the purpose of reassign_to_id, the required format choices, or the consequences of deletion. An agent has no way to correctly invoke this tool based on the given information.

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 0% — the description mentions none of the parameters. The schema defines pathParams (format, issueCategoryId) and queryParams (reassign_to_id), but neither the description nor the schema provides explanatory text. The description does nothing to clarify the meaning, purpose, or expected format of these parameters, and it does not compensate for the missing schema descriptions.

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 'Delete issue category' simply restates the tool name in plain English. It names a verb and resource but adds no additional specificity or distinction from siblings like deleteIssue or deleteProject. It is a tautology that provides no new information beyond the name itself.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, no mention of associated operations (e.g., reassigning issues via reassign_to_id), and no indication of constraints like whether deletion fails if the category still contains issues. The description offers zero usage context.

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