delete_label

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

With no annotations, the description carries the full burden for behavioral disclosure. It does state that deletion is permanent and cannot be undone, which is a critical trait. However, it does not mention side effects on cards using the label, any required permissions, or the purpose of the 'confirm' parameter, leaving gaps in 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 clear action statement and a short caution. Every word earns its place, and the caution adds important context without redundancy.

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 deletion tool with no output schema, the description covers the core purpose and permanence but lacks context about when to choose this over 'remove_label' and the operational side effects on cards that use the label. It is adequate but not fully complete.

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 describes all four parameters (fields, confirm, labelId, detailLevel) with full coverage, so the description does not need to add parameter details. The schema itself is sufficient, yielding a baseline score of 3.

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 'Permanently delete a label' uses a specific verb and resource, making the tool's purpose clear. However, it does not explicitly differentiate from the sibling tool 'remove_label', which could be confused with removing a label from a card, so it misses the top score.

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 includes only a caution 'Use this tool with caution as deletion cannot be undone', which is a warning rather than usage guidance. It provides no explicit when-to-use vs alternatives, no prerequisites, and no exclusions, so guidance is minimal.

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