Delete label

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

The annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is fully covered by structured data. The description adds nothing on top of that: it does not say the deletion is permanent, whether labels attached to issues are stripped, or how the required confirmation behaves. With annotations doing all the work, this is a bare-minimum score.

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 single sentence is front-loaded and free of filler, but that brevity comes from under-specification rather than economy. There is no structure to speak of and no sentence that conveys actionable 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?

For a destructive, zero-required-parameter, seven-parameter mutation with no output schema, the description supplies none of the missing context: no target identification, no confirmation workflow, no result behavior. Nothing an agent needs in order to call this correctly is present.

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?

Seven parameters with only 14% schema description coverage, and the description contributes zero parameter meaning. It never mentions name (presumably the target label), project_id/group scoping, or why update-style fields like new_name, color, and description exist on a delete tool — a genuinely confusing surface left entirely unexplained.

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?

"Delete a label." restates the tool name and title almost verbatim; the only added information is the resource type, which is already in the name. It does not distinguish this from siblings such as gitlab_delete_tag, gitlab_delete_milestone, or gitlab_update_label, so an agent learns nothing it did not already know from the identifier.

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 when-to-use guidance at all: no preconditions, no note that the label must exist or be scoped to a project/group, and no mention of alternatives like gitlab_update_label (to rename) or gitlab_get_label (to inspect first). An agent must infer everything from the name.

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