bulk_move

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

Annotations provide readOnlyHint=false (not read-only) and destructiveHint=false (not destructive). The description adds that it queries then moves in a batched AppleScript call, but does not elaborate on side effects, permissions, or whether the operation is reversible. It meets baseline but adds limited value beyond annotations.

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 two concise sentences, front-loading the core purpose and implementation detail. Every sentence adds value without unnecessary fluff.

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?

The tool has 6 parameters with 1 required, no output schema, and annotations only providing non-destructive hints. The description explains the high-level mechanism but lacks information about error handling, behavior when no messages match, rate limits, or the return value (e.g., number of messages moved). Adequate but with notable gaps.

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 description coverage is 100%, so all parameters are documented in the schema. The description reiterates 'by mailbox, sender substring, or both' which corresponds to 'mailbox' and 'from' parameters, but adds no new meaning beyond the schema definitions. 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 messages to a destination mailbox in one call' and specifies filtering by 'mailbox, sender substring, or both.' This distinguishes it from siblings like 'move_email' which handles single messages.

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 it is for batch operations by saying 'in one call' and mentions querying the Envelope Index, but it does not explicitly state when to use this tool versus alternatives (e.g., 'move_email' for single moves, 'empty_mailbox' for clearing a mailbox). No exclusionary guidance is provided.

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