delete_label

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

With no annotations, the description must carry the behavioral burden. It discloses the destructive nature via 'Delete' and adds an important permission constraint, but it does not mention whether deletion is permanent, cascades to tasks using the label, or requires additional safeguards.

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?

A single sentence states the action, the identifier, and the role requirement with no filler. The key information is front-loaded and easy to parse.

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 one-parameter destructive operation, the description gives the action, parameter, and authorization prerequisite, which is enough to select and invoke the tool. It omits side effects, but those are not strictly required for the call.

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?

Schema description coverage is 100%, so the label_id parameter is already documented; the description's 'by ID' adds no new semantic detail. It correctly aligns with the parameter but doesn't go beyond the schema.

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?

Description states the exact operation — delete a label — with the identifying key (by ID) and the required role. This clearly distinguishes it from label-related siblings like create_label, update_label, and list_labels.

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?

It communicates the prerequisite (owner or admin role) but does not say when to prefer delete_label over alternatives or mention any conditions against use. Usage context is implied by the action name rather than explicitly guided.

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