bulk_move

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

Disclosures include operations in one IMAP pass, dryRun support, and max batch limit. The annotation destructiveHint: false is consistent. No contradictions noted, but could mention that moves are reversible or if permissions required.

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 with no redundancy. Key information is front-loaded: purpose, usage, and differentiation.

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?

Covers essential aspects: method of selection (IDs or criteria), dryRun, batch size limit. Missing details on return value or error handling, but acceptable without output schema.

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?

With 100% schema coverage, the description adds value by explaining the XOR relationship between emailIds and match, and that folder is required when using match. This context goes beyond the schema 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 the action (move multiple emails), resource (emails in one IMAP pass), and explicitly differentiates from the sibling tool move_email for single-message moves.

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?

Provides explicit guidance: when to use (bulk moves), when not to use (single-message use move_email), and how to use (XOR between emailIds and match criteria, dryRun preview, max batch size).

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