move_email

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

The description carries the behavioral burden as annotations only include destructiveHint=false. It clarifies that the tool moves (not copies) a single email, and the get_folders advice implies the target must exist. No contradiction with 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?

Three sentences, all useful and front-loaded with the action. It includes usage guidance, alternatives, and a prerequisite without waste or redundancy.

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?

The tool is simple, no output schema, and the description covers what, when, and prerequisites. It could be more complete by noting the email is removed from the source folder, but the 'move' verb already implies this. Overall adequate for the complexity.

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 coverage is 50%: emailId is well-described, targetFolder is not. The description adds semantic context by referring to 'specified mailbox folder' and 'target folder path', but does not fully define the expected format or examples for targetFolder. It partially compensates for the coverage gap.

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 a single email to any specified mailbox folder' with a specific verb and resource. It distinguishes from sibling tools like archive_email, trash_email, and bulk_move by specifying single-email scope and custom folder targeting.

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?

Explicitly provides when to use: 'Use when routing a message to a custom folder.' It also names alternatives: 'Prefer archive_email to move to the standard Archive folder, or trash_email to move to Trash.' The prerequisite 'Use get_folders first to confirm the target folder path' adds clear guidance.

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