delete_issue_attachment

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not state whether deletion is permanent, whether any restore path exists (unlike delete_issue, which has restore_issue), or what permissions are required. 'using its unique identifier' is schema restatement, not behavioral disclosure.

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 where the second is a near-verbatim repeat of the first; the redundancy wastes space rather than adding value. The core intent is front-loaded, but the duplicated sentence should have carried new information (constraints, permanence, ordering) instead.

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 destructive, non-idempotent mutation with a nested two-field identifier and no output schema, the description omits the information an agent most needs: permanence of deletion, required privileges, and the error/return behavior when the attachment or issue does not exist. Neither the schema nor any structured field covers these, so the description leaves a real gap.

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% at the parameter level, and the only parameter is a nested object with two required fields. The description says 'its unique identifier' singular, which does not clarify that both an issueId and an attachmentId must be supplied nor how they relate. It fails to compensate for the documentation gap.

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 names a specific verb and resource (delete an attachment from an issue), so the operation is identifiable. However, the second sentence merely restates the first with no added information, and there is no differentiation from near-identical siblings such as delete_test_case_attachment or delete_test_result_attachment.

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?

There is no guidance on when to use this tool, what prerequisites exist, or how it relates to the attachment siblings (get_issue_attachments, post_issue_attachment, and the parallel test-case/test-result attachment deleters). Usage is left entirely to inference from the name.

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