move-message

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

No annotations provided, so description carries full burden. It states the tool moves a real message and includes safety warnings to confirm destination and message id. However, it lacks details on failure modes, reversibility, or permissions, which are important for mutations.

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: begins with usage context, then return value, then anti-guidelines, and finally safety notes. Every sentence serves a clear purpose without 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 move operation with 3 parameters and no annotations, the description covers purpose, when to use, what to confirm beforehand, and the return value. It is sufficiently complete for an agent to use the tool correctly, though it could mention edge cases like moving to the same mailbox.

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 low (33% with only account described). The description explains 'id' as the message identifier and 'mailbox' as destination folder but does not elaborate on format constraints or the 'account' parameter beyond the schema's brief description. It adds some value but does not fully compensate for schema gaps.

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 explicitly states 'moving a single message (by id) into another mailbox/folder' with clear verb and resource. It distinguishes 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?

The description provides explicit usage guidelines: 'Use when' for single message moves, 'Do not use when' for batch moves or deletions, and directs to sibling tools batch-move-messages and delete-message. It also advises using list-mailboxes to confirm destination.

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