batch-move-messages

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

Even with no annotations, the description thoroughly discloses behavior: warns 'moves many real messages at once', advises confirming destination and ids, and explains the id-pinning semantics of sourceMailbox/sourceAccount, including that ambiguous ids are refused. This exceeds typical transparency.

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 organized into clear labeled segments (Use when, Returns, Do not use, Safety, source instructions), all dense and non-redundant. It front-loads the primary use case before safety details, and every sentence earns its place.

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 use case, exclusion criteria, safety precautions, return values (moved/failed counts and reasons), and parameter pitfalls. With an output schema present and this level of contextual detail, the description is complete for a 5-parameter batch mutation tool.

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 schema leaves ids and mailbox without descriptions, but the description defines ids as 1-100 and mailbox as the destination. It also adds critical semantics for the sourceAccount/sourceMailbox pairing, clarifying their purpose and the failure mode. With 60% schema coverage, the description compensates the remaining gap effectively.

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 opens with a specific action: 'moving multiple messages (1–100 ids) into the same destination mailbox/folder in one call', clearly stating the verb, resource, and scope. It also explicitly contrasts with move-message and batch-delete-messages, making sibling differentiation strong.

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 'Use when' and 'Do not use when' conditions with named alternative tools, and additionally instructs to use list-mailboxes to confirm destination name. This gives unambiguous selection guidance.

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