mgmt_label_delete

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Delete label' without mentioning that deletion is likely irreversible, whether authentication or specific permissions are required, or any side effects on associated counters. This is a significant gap for a mutating operation.

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 short (a documentation URL plus 'Delete label'), which is concise, but the URL is not actionable guidance and the phrase lacks explanatory structure. It is not front-loaded with useful information; it is under-specified rather than efficiently informative.

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 operation, the description is incomplete. It does not explain what happens on success or failure, whether the operation is permanent, or any prerequisites. There is no output schema to compensate, and no behavioral context, leaving an agent without enough detail to safely invoke it.

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 has 100% description coverage: both 'pretty' and 'labelId' are described. The tool description itself adds no parameter-specific meaning, so the baseline of 3 applies. It does not clarify parameter formats or interactions 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?

The description states 'Delete label' which is a specific verb and resource. It clearly identifies the operation, and the tool name itself distinguishes it from sibling label operations like mgmt_label_get and mgmt_label_update. However, it adds no extra context about scope or what exactly is deleted (e.g., a specific label by ID), leaving it slightly minimal.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, when deletion is appropriate, or when to avoid it. With siblings like mgmt_label_update and mgmt_labels_list, an agent gets no routing hints from the description.

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