delete_label

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

With no annotations, the description carries the full burden of disclosure, but it only states the high-level action. It does not reveal whether the deletion is permanent, whether the label is removed from all cards using it, or whether special permissions are required.

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, clear sentence with no filler, making it easy to parse and front-loaded. It is efficient, though it could arguably be more informative without becoming verbose.

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 one-parameter delete tool with an output schema, the description is minimally adequate: it identifies the target resource and action. However, it omits side effects and fails to situate the tool relative to sibling operations like remove_label_from_card, leaving some gaps for an agent deciding how to fulfill a request.

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 lists only label_id with no description, and schema description coverage is 0%. The description adds no information about the parameter's format, origin, or constraints, leaving the agent fully dependent on the parameter name.

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 uses the specific verb 'Delete' with the resource 'label' and scope 'from a board', clearly distinguishing it from sibling tools like remove_label_from_card and delete_attachment. It is a precise and unambiguous statement of the tool's function.

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 about when to use this tool versus alternatives such as remove_label_from_card or archive_card. The description simply states the action without offering context, prerequisites, or exclusions.

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