Bulk Move Emails

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

The description discloses behavioral traits like progress notifications, return counts, and the silent no-op risk with incorrect sourceFolder. Annotations already indicate a write operation (readOnlyHint=false), and the description aligns with this, adding valuable context.

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 with three sentences: purpose, progress/returns, and detailed sourceFolder guidance. It is well-structured and front-loaded, though the third sentence is dense with information.

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 presence of an output schema, the description adequately covers core behavior, parameter nuances, and side effects. It is complete for a bulk move tool, though it could mention rate limits or confirmation steps.

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%, but the description significantly enhances parameter understanding, especially for sourceFolder, explaining IMAP UID scoping, pitfalls, and behavior of no-op moves. This goes well beyond the schema's brief descriptions.

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 'Move multiple emails to a folder in one call', providing a specific verb (move), resource (emails), and scope (multiple to a folder). This distinguishes it from siblings like move_email (single email) and bulk_move_to_label (different action).

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 on when to pass sourceFolder and warnings about using 'All Mail' as source. While it doesn't explicitly mention when to use alternative tools, the focus on bulk operations implies exclusivity.

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