email_move_messages

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

Without annotations, the description explains the key behavioral aspect: preference for UID MOVE and fallback to COPY+UID EXPUNGE. It also specifies the data moved (messages by UID). However, it doesn't disclose error handling, authorization needs, or what happens if some UIDs fail.

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 two sentences, front-loaded with the primary action, and each sentence adds essential information (purpose, fallback, precondition). No unnecessary words.

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 tool with three string parameters and no output schema, the description covers the main operation, fallback behavior, and a key precondition. It could mention error conditions or UID validity, but overall it provides sufficient context for correct usage.

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 0%, but the description indirectly defines each parameter: uids are the message identifiers, source_folder is the origin, destination_folder is the target. It adds the constraint that destination must exist. While not detailing format or constraints, it provides enough context for a straightforward tool.

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 tool moves messages with specified UIDs from source_folder to destination_folder, using UID MOVE with fallback. It distinguishes itself from sibling tools like email_list_messages or email_create_folder by specifying the move action.

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 gives explicit precondition that the destination folder must exist and refers to email_create_folder for that purpose. It also explains the fallback behavior, providing context on when it might behave differently. However, it doesn't explicitly contrast with other tools for copying or other operations.

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