gws.mail.create_label

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds behavioral context beyond annotations: it discloses the return value (new label ID) and the nesting behavior, which helps the agent anticipate outcomes. It does not cover rate limits or auth requirements but provides meaningful addition.

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 with no wasted words: the first states the core action, the second gives key usage detail and return value. Fully front-loaded and efficient.

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 create tool with 4 parameters and no output schema, the description covers the essential points: what it creates, how to structure the name, what it returns, and how to use the result. The color and account parameters are self-explanatory from the schema, so no additional context is needed.

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 100%, so baseline is 3. The description adds value by explicitly explaining the '/' nesting syntax for the 'name' parameter, which is not fully detailed in the schema. Other parameters are adequately described in the schema, so the description enhances the key parameter without redundancy.

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 'Create a new Gmail label' with a specific verb and resource. It also distinguishes from siblings like list_labels and modify_message by explaining the returned ID's purpose and the nesting syntax.

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?

Provides explicit guidance on nesting with '/', and explains the workflow: the returned ID is passed to mail.modify_message. This gives clear context on when and how to use the tool, effectively differentiating it from related operations.

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