deleteIssue

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

No annotations exist, so the description must bear the burden of behavioral disclosure. It only states 'delete', implying a destructive operation, but omits details on permanence, authorization needs, or side effects. A score of 2 reflects this significant gap.

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 (two words) but at the cost of informativeness. It is under-specification rather than efficient clarity, and lacks any structure or 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 nested parameter, lack of output schema, and no annotations, the description is woefully incomplete. It provides no context for the agent to understand preconditions, effects, or return value, making it nearly useless.

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 coverage is 0%, but the description adds nothing about the required nested parameters (format, issueId). The agent has to infer meaning solely from parameter 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?

Description 'Delete issue' is a tautology that restates the tool name without adding any context or specificity. It fails to indicate the resource type or scope, and does not differentiate from sibling delete tools like deleteAttachment or deleteGroup.

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. With many sibling delete tools, the agent has no indication of context or prerequisites, such as requiring an issue ID or permissions.

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