move_thread

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

Beyond annotations (destructiveHint=true, idempotentHint=true), the description adds that moving is destructive, describes cross-folder walking behavior, and the dry run preview mechanism. It does not cover error cases or permissions, but provides sufficient behavioral context.

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 three concise sentences, each adding distinct information: purpose, default vs. acrossFolders behavior, and dry run capability. No redundant or irrelevant content; front-loaded with the core action.

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 complexity (4 parameters, no output schema, destructive action), the description covers essential aspects: operation, parameter effects, and preview mode. It lacks return value details but is sufficient for selecting and using the tool correctly.

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?

The input schema covers all parameters with descriptions (100% coverage). The description adds value by integrating the parameters into the workflow, e.g., explaining the default scoping and the effect of acrossFolders, which complements the schema details.

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 'Move every message in a thread to a destination folder,' specifying the verb (move) and resource (thread messages). It distinguishes from siblings like move_message (single message) and bulk_move (arbitrary set), and explains the default scoping 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 explains when to use the acrossFolders and dryRun parameters to modify behavior, and implies that for single-message moves, move_message should be used instead. However, it does not explicitly list when not to use this tool or name alternative tools.

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