Move Email

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

The description explains the folder-scoped nature of IMAP UIDs and recommends passing sourceFolder, adding behavioral context beyond annotations. It does not mention failure modes, side effects, or whether moving is reversible, but annotations already indicate it is not read-only and not destructive, so the description is consistent and adds moderate value.

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 extremely concise at two sentences. The first sentence states the primary action, and the second provides critical guidance. No wasted words, front-loaded efficiently.

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 output schema exists and the tool has 4 parameters, the description covers the main action and a key nuance (sourceFolder). It does not address error handling or when to use specific sibling moves, but it is sufficiently complete for a move operation.

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?

With 75% schema description coverage, the description adds value by listing common targets for targetFolder and explaining the importance of sourceFolder. It compensates for the lack of schema description on emailId by providing critical usage nuance for sourceFolder.

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 clear. However, it does not explicitly differentiate from sibling tools like move_to_folder, move_to_trash, etc., which are more specific.

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 guidance on when to use the sourceFolder parameter (when UID came from non-INBOX folder), which is useful. However, it does not explain when to choose this generic move tool over specific alternatives like move_to_trash or move_to_folder.

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