delete_label

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

With no annotations provided, the description must bear full responsibility for disclosing behavioral traits. 'Delete' implies a destructive mutation, but the description does not mention permanence, side effects on issues, permissions required, or error conditions. This is a significant gap for a write operation.

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 description is a single concise sentence that is clear and front-loaded. It is not verbose and every word earns its place. However, it is so minimal that it misses opportunities to provide useful context, but structurally it is well-formed.

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 delete operation with no annotations and no output schema, the description is inadequate. It does not explain what happens after deletion, whether the label must be detached from issues first, or any potential impact. This leaves an agent without enough context to safely invoke the tool.

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?

The schema has 2 parameters with 50% description coverage (workspace_id has a description; id does not). The tool description adds no parameter information beyond the implication that 'id' refers to the label to delete. It fails to clarify the id format or how workspace_id interacts with the deletion.

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 'Delete an issue label' uses a specific verb ('Delete') and a resource ('issue label') to clearly identify the tool's action. It is unambiguous and distinct enough from sibling delete tools (e.g., delete_issue, delete_project) due to the unique resource type, though it does not explicitly differentiate itself.

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 versus alternatives, nor any mention of prerequisites or context. The description merely states the action without explaining situations where deletion is appropriate or how it relates to sibling tools like delete_issue or update_label.

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