bulk_move

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

Discloses use of a single IMAP session, atomic UID MOVE (RFC 6851) when supported, and fallback to COPY+STORE+EXPUNGE. This adds value beyond the basic purpose, though it does not cover authorization or error handling.

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 concise sentences, front-loaded with purpose. Each sentence adds necessary technical detail without redundancy.

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?

Provides core behavioral details (atomic MOVE, fallback, single session) but lacks output format, error handling, or idempotency info. For a bulk operation with no output schema or annotations, more detail is warranted.

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 has 0% description coverage and no parameter descriptions. The tool description does not add meaning to the three parameters (folder, email_ids, destination). With no param info in schema or description, the agent must infer meaning from names alone.

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?

Clearly states 'Move multiple messages to another folder in a single IMAP session'. The verb 'move' and resource 'multiple messages' are specific, and the description distinguishes from sibling tool 'move_email' (single move).

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?

Implies usage for bulk moves (e.g., when moving many messages) but does not explicitly state when to use vs alternatives like 'move_email'. No when-not or alternative names provided.

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