Move Email to Custom Folder

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

Annotations are all false (readOnlyHint, idempotentHint, destructiveHint), so the description must convey behavioral traits. It states 'Move an email' implying mutation, but does not disclose side effects like whether the original copy is deleted, whether the operation is reversible, or permission requirements. The detailed sourceFolder parameter description is in schema but not in main description.

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: two short sentences that front-load the core purpose and differentiate from a sibling. Every word contributes, no fluff.

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 of a move operation (especially with IMAP UID scoping and silent no-ops) and the presence of a detailed sourceFolder parameter, the description could be more complete. It does not mention important behaviors like what happens if the target folder doesn't exist, or strongly recommend providing sourceFolder. The existence of an output schema (not shown) mitigates but doesn't fully compensate.

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 75% (3 of 4 parameters have descriptions). The main description adds no parameter-level information beyond what's in the schema. It mentions 'Folders/' prefix but that is already implied by the folder parameter description. The emailId parameter lacks a description in the schema, and the main description does not address it.

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 custom folder' and specifies the path format 'Folders/<name>'. It distinguishes from sibling tool 'move_to_label' by noting similarity but different target type, helping the agent choose.

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 some context by comparing to move_to_label, but lacks explicit guidance on when to use this tool versus other move-related siblings like archive_email, move_to_spam, or bulk_move_emails. No prerequisites or exclusions mentioned.

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