delete_label

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Delete a label' without mentioning whether the delete is irreversible, if permissions are needed, or if there are side effects on issues or other linked data. This is a significant gap for a destructive mutation.

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 very concise, front-loaded with the one-line purpose, and has a clear arrow list for parameters. Every sentence is functional with no fluff. However, it might be slightly too terse given the lack of other context, but for conciseness and structure alone, it's well-organized.

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?

Given that this is a delete operation with no annotations, the description should provide more context such as irreversibility, required permissions, or effects on related data. It also does not mention what the return value or output looks like (though an output schema exists). The description is minimal and does not fully cover the operational context a delete tool requires.

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 description mostly restates the parameter names and adds 'UUID identifier', providing minimal extra meaning over the schema (which only has titles). Since schema description coverage is 0%, the description does compensate partially by clarifying that both parameters are UUIDs, but it doesn't explain the relationship between project_id and label_id (e.g., the label must belong to the project) or any validation constraints.

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 clearly states the tool's purpose: 'Delete a label.' It identifies the specific resource (label) and the action (delete), which distinguishes it from sibling delete tools for other resources like states and issue types. However, it doesn't mention any nuances like whether the delete is permanent or if there are any cascading effects.

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?

No guidance is provided on when to use this tool vs alternatives or any prerequisites. It simply states the action and parameters. For a destructive operation, it should mention that the label must exist, the project context is required, and consider exclusions (e.g., cannot delete if issues are associated). The lack of such context makes it hard for an agent to decide when or how to safely invoke it.

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