remove_labels

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

Annotations already indicate the tool is not read-only (readOnlyHint false), not destructive (destructiveHint false), idempotent, and open-world. The description adds context about preserving other labels ('leaving any remaining mailbox memberships alone'), which is a useful behavioral trait beyond what annotations provide.

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 highly concise with three sentences covering purpose, usage, and exclusion. Every sentence adds value, and the key information is front-loaded.

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 two parameters with full schema coverage, no output schema, and the complexity of a label removal operation, the description is complete enough for an agent to correctly select and invoke the tool. It covers what the tool does, when to use it, and when not to.

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 full description coverage (100%) for both parameters, so the schema already documents the parameters adequately. The description does not add significant new semantics beyond restating the schema purpose.

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 ('Remove one or more mailbox labels from an email') with a specific verb and resource. It distinguishes from sibling tools like add_labels and delete_email by specifying the scope of the operation.

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 explicit guidance: 'Use when the user wants to untag a specific message while leaving any remaining mailbox memberships alone' and a clear exclusion: 'Do not use to move an email to Trash; use delete_email.' This fully informs the agent about when and when not to use the tool.

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