taiga_delete_issue

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that deletion is permanent, which is a key behavioral trait. However, it omits other potentially important behaviors such as whether deletion is cascading, what happens to associated data, or whether special permissions are required.

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, concise sentence that front-loads the action and its key consequence. There is zero fluff or redundant information, making it highly efficient.

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 simplicity of the operation (one required parameter, no output schema), the description is largely complete. It states the purpose and permanence, which is sufficient for correct invocation, though it lacks explicit mention of what response to expect.

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 already fully describes the only parameter (issue_id) with 'Issue ID to delete' and 100% coverage. The description adds no additional semantic detail about the parameter, so the baseline score of 3 applies.

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 'Permanently delete an issue' uses a specific verb (delete) and resource (issue), clearly distinguishing it from sibling tools that operate on other resources. The qualifier 'permanently' adds critical detail about the operation's irreversibility, which is not directly visible from the tool name alone.

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 no guidance on when to use this tool versus alternatives such as taiga_edit_issue or taiga_get_issue. There is no mention of prerequisites, scenarios where deletion is appropriate, or warnings about using it instead of other operations.

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