move_emails

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

With no annotations, the description carries full burden for behavioral disclosure. It explains the use of UIDs and hints at folder discovery via list_folders, but does not mention side effects like flag preservation, permissions, or rate limits, which limits transparency.

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 concise with two sentences that contain no redundant information. It is front-loaded with the core action and adds a helpful pointer to list_folders, making it efficient.

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 simple move operation with no output schema, the description covers the essential: target folder and identifier usage. It could mention expected outcomes or errors, but given the straightforward nature, it is adequately complete.

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 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema: it reinforces using UIDs and suggests list_folders for folderName. No additional guidance on sourceFolder or parameter formatting is provided.

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 it moves emails to a specified folder using UIDs, and notes UIDs are permanent identifiers. It effectively distinguishes the action from siblings like archive or delete, although it could elaborate on the move semantics (e.g., source removal).

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 suggests using list_folders to see available folders, providing useful context. However, it lacks explicit guidance on when to prefer move_emails over archive_emails or delete_emails, nor does it specify prerequisites or when not to use it.

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