move-email-batch

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

No annotations are provided, so the description carries full burden. It discloses that the tool moves emails using sequence IDs, but does not specify behavioral traits such as whether the operation is destructive, permission requirements, batch limits, or return behavior. This is insufficient for a batch mutation tool.

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 a single sentence (16 words) that front-loads the core action and target. No redundant information. Highly efficient.

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 absence of an output schema and the nature of a batch operation, the description should explain return values, success/failure indicators, and potential limitations (e.g., max batch size). None of this is provided, leaving the agent without critical information.

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% with both parameters described. The description adds minor context by specifying that IDs come from search results, which is slightly helpful beyond the schema. Baseline 3 is appropriate.

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'), target ('to a specific folder/label'), and method ('using their sequence IDs from search results'). It distinguishes itself from sibling tools like 'move-email' (single) and 'apply-label-batch' (apply vs 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?

The description implies usage when the agent has multiple email sequence IDs from search results, but does not explicitly state when to use this tool over alternatives like 'move-email' (single) or 'apply-label-batch' (different operation). No exclusions or conditions are mentioned.

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