delete_issue

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

The description adds that 'Uses default session if session_id not provided', which is a behavioral detail beyond the schema. However, with no annotations, it fails to disclose important aspects like permission requirements, reversibility, or side effects (e.g., cascading deletes).

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?

Two sentences, front-loaded with the core action. Every word earns its place. No extraneous information.

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 output schema exists (though not shown), the description is adequate for a simple deletion. However, lacking details on error handling, idempotency, and permissions makes it less complete for a tool with 2 parameters.

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?

With 0% schema description coverage, the description provides minimal meaning: it implies issue_id is the ID to delete, and explains session_id's default behavior. No details on issue_id format, range, or constraints.

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 'Deletes an issue by its ID' clearly specifies the action (delete) and resource (issue) with identifier. It is straightforward, but does not differentiate from similar delete sibling tools like delete_task or delete_epic.

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 on when to use this tool vs alternatives (e.g., update_issue, resolve). No mention of prerequisites or context such as whether the issue must be in a certain state.

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