delete_label

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds no behavioral context beyond the operation itself. It does not mention irreversibility, project scoping, or potential effects on referenced data, missing an opportunity to enrich the annotation-provided safety signal.

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, front-loaded sentence with no verbose or redundant wording. It is appropriately concise for a delete operation, though it sacrifices useful context for brevity.

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 operation with no output schema and two opaque parameters, the description is extremely thin. It lacks details about project scoping, irreversibility, or impact on associated work items, which would be expected given the tool's destructive nature and sibling context.

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 input schema has 0% description coverage, and the description does not compensate. It only says 'by ID' but fails to explain the role of project_id or that both IDs are required. The relationship between label_id and project_id is left entirely to the schema parameter names alone.

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 action ('Delete') and the resource ('a label'), which directly distinguishes it from sibling delete_* tools like delete_project or delete_work_item. The phrase 'by ID' aligns with the label_id parameter, making the purpose unambiguous.

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 versus alternatives such as update_label or retrieve_label, nor any context about prerequisites or exclusions. The description simply states the operation without situating it within a workflow.

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