delete_label

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's mention of 'deletes' aligns but adds no new behavioral context. No additional traits (e.g., permissions, side effects) are disclosed.

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?

Two sentences, but the first sentence is verbose and introduces irrelevant functionality ('Create and manage'). The second sentence is clear. Could be trimmed to focus solely on deletion.

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?

As a destructive tool, the description lacks details on consequences (e.g., cascade effects on label assignments), return values, or required permissions. No output schema exists, so more context is necessary.

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?

Schema coverage is 50% (only customerContext has description). The tool description does not describe the 'id' parameter or add meaning beyond the schema. It misses the opportunity to clarify that 'id' likely refers to the label's unique identifier.

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 'Deletes the label specified by the Id' which clarifies the delete action, but the opening phrase 'Create and manage labels' is misleading and suggests a broader purpose. The tool name 'delete_label' reinforces the delete function, but the description's first sentence conflicts.

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 on when to use this tool versus alternatives like create_label or update_label. The description does not specify prerequisites, when not to use, or context for deletion.

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