move-message

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

With no annotations, the description carries the full burden. It states 'moves a real message between folders' and includes a safety note to confirm the destination mailbox and message id. This discloses the mutating nature and suggests pre-checks, though it doesn't cover error conditions or permissions.

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 and well-structured into 'Use when', 'Returns', 'Do not use when', and 'Safety' sections. Every sentence provides actionable value with no 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?

For a state-changing tool with an output schema, the description covers purpose, usage, alternatives, return value, and safety. It could mention edge cases (e.g., invalid id or mailbox) but is sufficiently complete for an agent to select and invoke the tool correctly.

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 only 33% (only 'account' has a description), so the description adds meaning for 'id' and 'mailbox' by indicating they refer to the message being moved and the destination folder. However, the optional 'account' parameter is not explained, leaving a minor 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 the tool's purpose: 'moving a single message (by id) into another mailbox/folder'. This is a specific verb+resource combination and distinguishes it from siblings like batch-move-messages and delete-message.

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: moving a single message...') and when-not-to-use ('Do not use when: moving several at once... or deleting...') with named alternatives (batch-move-messages, delete-message). Also advises using list-mailboxes and search-messages/list-messages as prerequisites.

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