delete_issue_type

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

With no annotations, the description needed to disclose side effects (e.g., whether deletion is permanent, what happens to associated issues, required permissions), but it only states 'Delete an issue type' providing no behavioral context beyond the action itself.

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 extremely concise, with a one-line purpose followed by a clear Args section. No superfluous content is present, and the structure front-loads the primary action.

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?

While the tool is simple, the description is incomplete for a destructive operation: it omits any caveats, permissions, or consequences of deletion. The presence of an output schema explains return values but does not compensate for missing behavioral and usage context.

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?

The schema has no descriptions, but the description clarifies each parameter as 'UUID identifier of the project' and 'UUID identifier of the issue type', adding meaning beyond the schema's generic titles of 'Project Id' and 'Issue Type Id'.

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 deletes an issue type, using a specific verb and resource. It distinguishes from sibling CRUD operations like create_issue_type, update_issue_type, and get_issue_type.

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, any prerequisites, or alternatives. It only states the action without any contextual cues about appropriate usage.

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