Move Email

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the verb 'Move' and does not disclose side effects such as removal from the source folder, irreversibility, permissions, or what happens if the destination folder does not exist. It adds no behavioral context beyond the obvious action.

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 a single, front-loaded sentence with no filler or redundant phrases. Every word is meaningful and directly communicates the operation.

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 and its three parameters are fully documented in the schema, so an agent can determine how to call it. However, since no annotations exist and the move is effectively destructive, a brief note about source-removal behavior or return value would round out the description.

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 100%, so the schema already documents all parameters: uid, to_folder, and from_folder. The description adds no parameter-level detail beyond what the schema provides, meriting the baseline score of 3.

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 uses a specific verb 'Move' and identifies the resource 'email' with a destination qualifier 'different IMAP folder'. It clearly distinguishes this operation from sibling tools like delete_email, fetch_email, or create_folder.

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 clearly conveys the action and context: moving an email between IMAP folders. It does not explicitly mention when to avoid this tool or suggest alternatives, but the context is unambiguous and sufficient for basic selection.

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