gmail_create_label

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

With no annotations, the description carries the transparency burden. It discloses the primary side-effect that a label is created and meaningfully explains that a slash in the name creates nested labels, which is real behavioral context. However, it does not disclose duplicate-label behavior, idempotency, permissions, or what happens to parent labels.

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 two sentences, front-loaded with the core action, and contains no filler. The nesting example earns its place because it clarifies a non-obvious usage pattern.

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?

The description is minimally adequate for a create-type tool with 6 parameters and 2 required fields, especially since the schema documents several parameters. It leaves gaps around duplicate label creation, parent label treatment, and expected return values, making it acceptable but not thorough.

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%, and the description adds important meaning to the 'name' parameter by showing that 'Clients/Acme' creates a nested label. It does not, however, compensate for the remaining param detail or clarify the expected palette/visibility parameter behavior beyond what the schema already provides.

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 a specific action and resource: create a Gmail label. It also adds the distinctive nesting behavior via path names, which helps distinguish it from sibling label tools like update, delete, and list labels.

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 gives no guidance on when to use this tool versus alternatives such as gmail_update_label or gmail_create_filter. There are no prerequisites, exclusions, or explicit selection criteria beyond the basic 'create a label' intent.

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