mail_move_message

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

Annotations already indicate non-destructive and non-read-only. Description adds 'recoverable — just relocates it' which reassures about safety, but omits other behavioral aspects like effect on flags or error conditions.

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?

Extremely concise, single sentence with no wasted words. Front-loaded with main action. However, could benefit from slightly more detail without losing conciseness.

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?

Given 6 parameters and no output schema, the description is sparse. Does not explain what happens if mailboxes don't exist, whether messageId is optional, or return value. Incomplete for a tool of this complexity.

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?

Only one parameter (destAccountName) has a description in the schema; the tool description adds no parameter details. Schema coverage is very low at 17%, and the description does not compensate by explaining required or optional parameters.

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?

Clearly states 'Move a message to a different mailbox' with the verb, resource, and destination. Includes clarification 'recoverable — just relocates it' to distinguish from deletion, which is relevant given siblings like mail_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?

Implies usage for moving messages (not copying or deleting), but no explicit guidance on when to use versus alternatives like mail_copy_message or when not to use. Lacks context clues for agent decision-making.

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