Delete Label

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

No annotations are provided, so the description carries the full disclosure burden. It conveys only that this is a destructive mutation; it says nothing about irreversibility, whether the label is also stripped from every card that carries it, permission requirements, or success/failure behavior.

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?

One short, front-loaded sentence with no padding or redundancy. Its terseness is efficient, though the brevity comes at the cost of the behavioral detail noted elsewhere.

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 tool with zero annotation coverage and no output schema, the definition omits the facts an agent most needs: whether deletion is permanent, whether it cascades to cards, and required scoping/permissions. The complete single-parameter schema is the only thing making this callable.

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 single parameter has 100% schema description coverage ('ID of the label to delete'), so the schema already carries the semantics. The description adds nothing about the identifier's format or where it comes from (e.g., get_board_labels), leaving this at the baseline.

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?

States a specific verb (delete) and resource (label) with a scoping qualifier ('from a board'), so the agent can tell it acts on the board's label taxonomy rather than on a card-label association. It stops short of naming the ambiguous siblings (remove_label_from_card, update_label) to differentiate itself explicitly.

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?

There is no statement of when to use this versus remove_label_from_card (detach a label from one card) or archive/update_label. The phrase 'from a board' faintly implies board-level scope, but no condition or alternative is spelled out.

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