bulk_move_messages

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

No annotations are provided, so the description carries the full disclosure burden. It signals batching ('in one call') but says nothing about permissions needed, behavior on unknown message ids or missing folders, whether the batch is atomic or partially applied, or batch size limits — significant gaps for a 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?

One sentence, front-loaded with the verb and resource, with zero filler. It is efficient, though the terseness leaves little room for the behavioral and parameter detail a bulk mutation tool arguably needs.

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?

With no annotations, no output schema, and 0% schema description coverage, the description should cover more: mutation semantics, failure modes, and return/confirmation behavior are all absent. An agent can form a call but cannot anticipate how errors or partial failures are handled.

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 0%, so the description must compensate, and it does partially: message_ids accepts 'refs or raw ids' and destination_folder accepts an 'id or well-known name.' This adds real meaning beyond the bare string/array types, but leaves 'ref' undefined and gives no examples for either parameter.

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?

States a specific verb and resource ('Move many messages') plus the bulk scope 'in one call,' which implicitly separates it from the sibling move_message. It does not explicitly name that sibling, but an agent can distinguish bulk from single-message moves without reading the schema.

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?

Usage is implied by 'many messages ... in one call,' suggesting it is for batch relocation rather than single moves. However, there is no explicit when-to-use/when-not guidance, no mention of when to prefer bulk_by_query or move_message, and no note on prerequisites such as folder existence.

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