move_thread

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

Description reveals that it searches specific headers and can search across Sent/All Mail. Annotations indicate destructiveHint=false, consistent with move being non-destructive. Could be more explicit about how it handles messages in different folders when acrossFolders is false.

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 sentences, front-loaded with key action, no redundant words. Efficiently communicates purpose and key option.

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?

No output schema, and description omits return value or confirmation. For a move operation, agents would benefit from knowing if success/error/items moved are returned.

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?

Description clarifies acrossFolders and the meaning of messageId. However, dryRun parameter lacks explanation both in schema and description. Schema coverage is 75%, so description partially compensates but misses a 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?

Description clearly states the tool moves all messages in a thread by searching Message-ID and References headers to a destination folder. It's distinct from siblings like move_email (single email) and delete_thread.

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 explains when to use acrossFolders to broaden search. However, it doesn't explicitly state when not to use this tool or contrast it with alternatives like move_email or apply_thread_action.

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