deleteIssueCategory

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Delete' which implies mutation, but omits critical details such as whether issues in the category are deleted or reassigned, whether deletion is permanent, and the role of the reassign_to_id query parameter. The schema hints at reassignment but the description is silent.

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 phrase, which is front-loaded and free of fluff. However, it is excessively terse and lacks the structural guidance (e.g., a second sentence on behavior or parameters) that would make it genuinely helpful.

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 presence of three parameters, a nested object structure, and no annotations or output schema, the description is grossly incomplete. It fails to cover how to use the tool, what the reassign parameter does, or any side effects, making it impossible for an agent to invoke it correctly with confidence.

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%, so the description must compensate by explaining parameter meanings. It provides none. The agent must infer the purpose of format, issueCategoryId, and reassign_to_id solely from their names, which is insufficient for correct invocation.

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 action ('Delete') and the resource ('issue category'), using a specific verb+resource structure. It effectively distinguishes this tool from sibling tools like deleteIssue, deleteProject, and the create/update/get issue category variants.

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?

No guidance is provided on when to use this tool versus alternatives, nor any context about prerequisites (e.g., whether the category must be empty) or when reassignment is needed. The description offers no exclusions or alternative tool references.

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