Bulk Move Emails to Label

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

Beyond annotations, the description adds key behaviors: emails remain in original folder, appear under Labels/{label}, and progress notifications for large batches. It does not mention idempotency or failure modes, but covers important side effects.

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?

Three concise sentences: action, effect, notification. No filler, front-loaded with purpose. Every sentence adds value.

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 output schema exists, return values need not be explained. The description covers core behavior and progress. It could mention the need for sourceFolder to avoid silent no-ops, but that is detailed in the schema. Overall fairly complete.

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 description coverage is 75% (3 of 4 params have descriptions), so baseline is 3. The main description adds no parameter-specific meaning beyond the schema. emailIds lacks description, but overall the schema carries the burden.

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 tool applies a label to multiple emails, distinguishes from bulk_move_emails (which moves folder) and bulk_remove_label (opposite). It also clarifies behavior (remains in original folder, appears in Labels/{label}).

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 use for batch labeling but does not explicitly contrast with single-email alternatives (move_to_label) or when not to use (e.g., for removing labels). It provides good context but lacks explicit usage guidance.

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