Delete Label

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

Description adds 'Irreversible' and 'Requires name or label_id' beyond annotations. Annotations already indicate destructiveHint=true, but the description clarifies parameter constraints (at least one identifier required) and emphasizes permanence.

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 concise sentences with no unnecessary words. Front-loaded with action and key traits (permanent, irreversible), followed by parameter guidance and pre-check recommendation.

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, parameter requirements, and pre-check. For a simple delete operation without output schema, this is nearly complete. Lacks mention of what happens on failure or return format, but not critical.

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%, so description must compensate. It states 'Requires name or label_id', clarifying that at least one of these is needed, but does not explain their format or relationship. This adds some value but not full detail.

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 explicitly states 'Delete a label permanently' with a clear verb and resource, differentiating it from sibling delete tools like gitlab_delete_branch or gitlab_delete_issue.

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?

Provides a recommended pre-check (gitlab_get_label or gitlab_list_labels) to verify existence before deletion, guiding appropriate usage. However, it does not explicitly state when not to use the tool or mention alternatives.

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