Move messages in bulk

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

Adds significant behavioral context beyond annotations: the required dry-run/confirmation gate is disclosed. This explains safe usage despite mutation (readOnlyHint=false) and non-destructive hint, making the tool's workflow transparent.

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?

Two concise sentences, front-loaded with purpose and gate. No filler or repetition of schema details.

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 gated workflow is clear, and annotations cover safety profile. However, no output schema and no explanation of return values or to_folder semantics leave some ambiguity for a 6-parameter 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?

Schema covers 67% of parameters. Description adds meaning for dry_run and confirmed via the gating phrase, but the required to_folder parameter remains undocumented in both schema and description. No clear explanation of how 'Trash' maps to to_folder.

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?

Description uses specific verb+resource+scope: 'File or Trash many messages at once.' This clearly distinguishes it from sibling tools like move_to_folder (singular) and bulk_apply_label (labels, not moves).

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?

Description explicitly provides a two-step usage protocol: 'preview with dry_run=true, show the user, then call with confirmed=true.' It implies bulk use but does not explicitly state when to prefer singular alternatives like move_to_folder.

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