Move Email

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds important behavioral traits: IMAP UID scoping issue, potential silent no-op if sourceFolder is wrong, and that moving to the same folder is a no-op. It doesn't discuss reversibility or error handling, but covers the key gotchas.

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, no filler. The first sentence states the action and lists common folders. The second provides critical guidance on sourceFolder. Every sentence earns its place.

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 3 parameters (2 required), schema descriptions for 2, output schema present, and annotations available, the description covers all essential usage details. It explains the key IMAP nuance and common targets, making the tool easy to use 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 provides descriptions for targetFolder and sourceFolder (67% coverage). The tool description adds value by explaining common target values and the critical IMAP UID context for sourceFolder, which goes beyond the schema. The emailId parameter lacks schema description but its purpose is self-evident from the tool name.

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 the action: 'Move an email to a different folder.' It lists common target folders (Trash, Archive, Spam, INBOX, Folders/MyFolder), distinguishing it from sibling tools like archive_email or move_to_trash which are specific cases. The verb 'move' and resource 'email' are explicit.

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 explicit guidance on when to use the sourceFolder parameter: 'Pass sourceFolder whenever the UID came from a folder other than INBOX — IMAP UIDs are folder-scoped.' It also warns against using 'All Mail' as source and notes that moving to the same folder is a no-op. This tells the agent exactly when and how to use the tool vs alternatives.

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