Bulk Move Emails to Label

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

Annotations indicate non-readonly, non-destructive, and non-idempotent. The description adds that emails remain in original folders, appear under Labels/, and progress notifications are sent for large batches. No contradictions with annotations.

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 action is front-loaded and the explanation of behavior is concise yet 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 complexity of batch labeling with folder-scoped UIDs, the description covers key behavioral aspects (original folder, progress notifications) and assumes the output schema handles return values. Could mention error handling or idempotency, but overall adequate.

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 description provides no information about the three parameters (emailIds, label, sourceFolder). Schema coverage is 67% (two of three params have descriptions in schema), which is moderate but not high enough to baseline at 3. The description does not compensate for the missing parameter details.

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 and explains that emails remain in their original folder, distinguishing it from move operations. The verb 'apply' and resource 'multiple emails' are specific.

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 labeling multiple emails but does not explicitly mention when to use this tool versus alternatives like bulk_remove_label or move_to_label. No when-not-to-use guidance is provided.

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