delete_issue_by_issue_id

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the 'Delete issue' text plus DELETE method aligns with them. The description adds no additional context such as whether the action is permanent, whether related data is affected, or whether special permissions are required, but it also does not contradict the annotations.

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 compact and front-loaded with the purpose and endpoint. It has no filler, though the Args line is redundant with the schema and could be omitted without losing meaning.

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 one-parameter delete operation with annotations and an output schema, the core essentials are present: the action, endpoint, and required id. However, the absence of usage guidance and any behavioral depth beyond the annotations leaves it merely adequate rather than fully complete.

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 only parameter is described as 'Args: issue_id: Issue ID,' which essentially repeats the schema's title 'Issue Id.' With schema description coverage at 0%, the description needed to compensate by adding format, example, or sourcing guidance, but it does not.

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 opens with 'Delete issue,' naming the exact action and resource, and also provides the HTTP endpoint DELETE /api/v1/issue/{issueId}. This is unambiguous, though it does not explicitly distinguish itself from sibling tools like delete_issue_comment_by_comment_id.

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 given on when to use this tool versus alternatives. The description does not mention when deletion is appropriate, what prerequisites exist, or how it relates to other issue-related tools. An agent receives no routing context among the many sibling tools.

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