gmail_delete_label

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly. It discloses that without confirm:true the call only reports and changes nothing, that deletion is permanent, and that messages are preserved but lose their categorization. These are exactly the critical behavioral traits an agent needs before invoking a mutation.

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 compact and front-loaded: a direct action statement followed by two crucial caveats about the confirm flag and message preservation. Every sentence contributes essential information and there is no filler.

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 three-parameter tool with no annotations and no output schema, the description covers purpose, safety, permanence, and side effects well enough for correct invocation. The only meaningful gap is that it does not describe the dry-run report format or successful response, but this is minor for a delete operation.

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 description adds real meaning to confirm by explaining the dry-run behavior beyond the schema's simple 'Must be true to actually delete.' However, the primary label parameter has no schema description and the tool description never clarifies whether a label ID, name, or display string is expected, leaving the most important parameter partially under-specified.

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 opens with a specific action and resource: 'Delete a Gmail label.' It adds meaningful boundary conditions by stating that deleting a label does not delete messages and that categorization is lost permanently, which distinguishes it from broader message-deletion tools and from sibling label tools.

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 implies when the tool should be used by explaining the confirm-gated dry run and the permanent loss of label categorization. However, it does not explicitly name alternatives such as gmail_update_label for preserving categorization or otherwise state when not to use this tool.

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