delete_label

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

The description only repeats the delete action, which is already captured by the destructiveHint annotation. It adds no new behavioral context such as reversibility, impact on associated work items, permission requirements, or error conditions. Given annotations already convey destructiveness, the description fails to provide additional transparency.

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 extremely concise: one sentence for purpose and a minimal args list. Every part is necessary and no words are wasted. It is well structured with a clear separation of function and parameters.

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 simple delete tool with annotations covering idempotency and destructiveness, the description is mostly adequate. However, it omits important context such as whether deletion cascades, if the label must exist, or how to obtain the IDs. Missing details reduce completeness for an agent operating in a complex environment with many sibling tools.

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?

With 0% schema description coverage, the description compensates by listing both parameters (project_id and label_id) and briefly explaining each as a UUID. This adds meaning beyond the schema's type-only definitions, though it lacks further details like format constraints or examples.

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 'Delete a label by ID', specifying the action (delete) and resource (label). While it doesn't explicitly distinguish from siblings, the verb itself differentiates it from create, update, and retrieve operations. It is concise and 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?

The description provides no guidance on when to use this tool versus alternatives like manage_work_item_label or update_label. There is no mention of prerequisites, scenarios, or conditions for deletion, leaving the agent to infer usage context from the name alone.

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