Move Email

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

Annotations are not contradictory and indicate a non-read-only, non-destructive operation. The description adds behavioral insights: the 'confirmed' requirement for Trash/Spam, the folder-scoping of IMAP UIDs, and warnings about 'All Mail' and no-op moves. This context is valuable beyond the annotations.

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 with four sentences but front-loaded with the core action. It efficiently covers key points without redundancy. Could be slightly more structured, but overall lean and effective.

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 (5 parameters, output schema present), the description covers essential use cases, parameter dependencies, and common pitfalls. It does not explain return values or error conditions, but the output schema presumably handles that. Adequately complete for the context.

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 description coverage is high (80%), so the baseline is 3. The description adds value by explaining the 'confirmed' requirement in context and elaborating on 'sourceFolder' with IMAP UID scoping and the 'All Mail' pitfall. It goes beyond the schema descriptions.

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 an email to a different folder' with specific verb and resource. It lists common targets, making the purpose obvious. However, it does not explicitly differentiate from sibling tools like 'move_to_folder' or 'move_to_trash', which could cause ambiguity.

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 provides clear conditions for using 'confirmed' and 'sourceFolder' parameters, but lacks explicit guidance on when to choose this tool over specialized siblings like 'move_to_spam' or 'move_to_trash'. The usage context is implied through examples but not fully detailed.

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