delete_issue_task

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the agent knows this is a destructive, non-idempotent operation. The description adds nothing beyond this, such as whether the deletion is permanent, whether it cascades to related test results, or what permissions are required. With annotations covering the basic safety profile, the description should still provide additional behavioral context, which it fails to do.

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 consists of two sentences that convey the same information, with the second being a redundant restatement of the first. This is not concise; it wastes space on repetition rather than providing useful details. The structure is not front-loaded with any additional context.

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 tool's complexity (nested object parameters, no output schema, destructive operation), the description is inadequate. It omits critical details such as the required parameters (issueId and taskId), the scope of deletion, and any behavioral caveats. With no output schema and 0% schema description coverage, the description should carry more burden but does not.

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%, meaning the schema itself provides no descriptions for the nested 'path' object or its 'issueId' and 'taskId' properties. The description only says 'using its unique identifier,' which is vague and does not compensate for the missing parameter documentation. The agent cannot determine from the description alone that two parameters (issueId and taskId) are required.

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 states a clear verb+resource ('Delete a task'), but the second sentence merely restates the first. It does not differentiate from siblings like delete_issue (which deletes an issue, not a task) or delete_issue_test_result, leaving the agent to infer the distinction from the 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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that this deletes a task within an issue, nor does it clarify its relationship to other deletion tools such as delete_issue or delete_issue_attachment. There is no when-to-use or when-not-to-use information.

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