Bulk Remove Label from Emails

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

Annotations indicate this is a non-read-only, non-destructive, non-idempotent mutation. The description adds context by explaining that emails are removed from Labels/{label} but remain in original folders, and warns about the UID space issue, which goes 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 concise at two sentences, front-loaded with the action, and contains no unnecessary words. Every sentence is informative.

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 tool's complexity (bulk operation with UID nuance) and the existence of an output schema, the description covers the essential behavioral context and constraints. It could briefly mention error handling or atomicity, but is largely complete for an agent to use correctly.

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 already describes parameters well (100% coverage). The description reinforces the critical nuance that emailIds must be UIDs from the specific label folder, adding value beyond the schema alone by emphasizing the potential for silent failure.

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 'Remove a label from multiple emails', providing a specific verb and resource. It distinguishes this tool from siblings like 'remove_label' (singular) and other bulk operations by specifying that emails remain in their original folders.

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 critical guidance that UIDs must be from the Labels/{label} folder, warning that INBOX UIDs will silently miss. This effectively tells when to use the tool and when not to, though it does not explicitly name alternative tools for different scenarios.

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