Move an email from one folder to another by UID to organize mailbox messages into the correct folders.
Move an email from one folder to another using its UID. Useful for organizing emails into different mailbox folders.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | ||
| sourceFolder | Yes | ||
| targetFolder | Yes |
Changes observed during successful MCP inspections.
v1.0.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full behavioral burden. It does not disclose whether the move is destructive to the source folder, whether it requires specific permissions, whether the email is copied or truly moved, or what happens on UID conflicts.
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 short sentences, front-loaded with the primary action. No wasted words, though the second sentence ('Useful for organizing...') adds little informational value.
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?
For a mutation tool with no annotations, no output schema, and 0% parameter description coverage, the description is inadequate. It omits critical operational details such as folder identifier format, error conditions, and side effects.
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 0% for 3 required parameters. The description does not explain what sourceFolder and targetFolder should contain (names vs. paths vs. IDs), nor does it clarify the UID type or format. The description only restates the obvious parameter purpose.
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?
States a specific verb and resource ('Move an email') and the identifier used ('UID'). It is distinguishable from sibling tools like deleteEmail, but it does not explicitly differentiate itself from other folder-management siblings such as listFolders.
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 offers a vague purpose ('Useful for organizing emails'), but provides no when-to-use/when-not-to-use guidance and does not mention alternatives like deleteEmail or searchEmails. There is no routing guidance for the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.