Delete Issue Link

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

Description adds 'Irreversible for that relation' beyond annotations (destructiveHint=true). Provides context on permanence, though annotations already indicate destructive nature.

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?

Three concise sentences, front-loaded with action. No fluff; every sentence adds value.

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?

Covers purpose, irreversibility, required params, and pre-check. No output schema, but for a delete operation this is adequate. Could mention confirmation or error handling.

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%. Description only names required parameters ('issue_iid' and 'issue_link_id') without explaining their meaning or format, failing to compensate.

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 clearly states 'Delete an issue link permanently.' Verb 'Delete' + resource 'issue link' is specific. Distinguishes from sibling create_issue_link.

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?

Explicitly requires 'issue_iid' and 'issue_link_id' parameters and recommends pre-check with 'gitlab_get_issue_link' or 'gitlab_list_issue_links', providing clear when-to-use and alternatives.

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