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 burden of behavioral disclosure. While 'Delete' implies a destructive, irreversible operation, the description doesn't specify permissions required, whether deletion is synchronous or asynchronous, error conditions (e.g., if the label doesn't exist), or side effects. For a destructive tool with zero annotation coverage, this is inadequate.

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, direct sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place by conveying essential information 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?

Given the tool's destructive nature, lack of annotations, no output schema, and undocumented parameters, the description is insufficient. It doesn't explain what happens upon deletion, error handling, or return values. For a high-stakes operation like deletion, more context is needed to ensure safe and correct usage.

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 2 required parameters (key and value) with 0% description coverage, meaning neither parameter is documented in the schema. The description adds no information about what these parameters represent, their format, or examples (e.g., whether 'key' is a label name and 'value' is its value). This leaves the agent guessing about proper usage.

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 clearly states the action ('Delete') and the resource ('a label in the PCE'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'create-label' and 'update-label' by specifying the destructive operation. However, it doesn't specify what 'PCE' stands for or provide additional context about the label system.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., the label must exist), consequences (e.g., what happens to workloads using this label), or when to choose deletion over updating. With siblings like 'update-label' and 'get-labels' available, this lack of differentiation is a significant gap.

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