Bulk move

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

With no annotations, the description carries full burden. It discloses provider-specific behavior (Gmail adds label and removes from Inbox, others move to folder), mentions destructive nature via the confirm parameter, and notes capping with max. However, it does not detail potential impacts on thread structure or mention whether moved messages are archived.

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 concise, one sentence with a parenthetical clarification for provider differences. It efficiently conveys the core purpose, though it could be slightly more structured with separate notes for behavior and safety.

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 7 parameters, full schema coverage, and no output schema or annotations, the description fairly covers the operation's scope and provider behavior. It could be improved by explicitly stating it operates on individual messages (not threads) and what the return value indicates, but it is largely adequate.

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%, so parameters are fully described in the schema itself. The tool's description adds no extra parameter-specific meaning beyond the schema, warranting the baseline score of 3.

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 verb (file/move) and resource (messages matching a query) and distinguishes the tool from siblings like move_message (single message) or bulk_delete (deletion) by specifying it moves to a label/folder and describes provider-specific behavior.

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 for bulk moving messages based on a query, but does not explicitly state when to avoid it or compare with alternatives like bulk_modify_labels or bulk_trash. Lacks explicit exclusions or recommendations.

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