Move Mail

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

With no annotations provided, the description carries the full transparency burden. It does disclose the required delegated Mail.ReadWrite permission, which is useful. However, it does not mention the destructive nature of moving (removing from the source folder) or any other side effects, limiting full behavioral 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 and front-loaded with the primary action and required permission. The Chinese translations add multilingual value without bloating the content. Every sentence serves a purpose.

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 the simple 2-parameter tool, the description covers the core purpose and permission. It does not explain return values or side effects in detail, but the absence of an output schema reduces that need. Overall, it is adequately complete for this action.

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?

The schema covers 100% of parameters with descriptions. 'Message ID' and 'Destination folder ID from mail_list_folders' already provide meaning. The tool description adds no additional parameter explanations beyond the schema, so it holds to the baseline without enhancing semantics.

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 'Move a message to a target mailbox folder' with a specific verb and resource. It distinguishes itself from sibling tools like mail_copy_message and mail_delete_message by the unique move action. The inclusion of Chinese intents reinforces the purpose without ambiguity.

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 explains what the tool does but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like mail_copy_message when duplication is needed, nor does it specify exclusions. The context is clear but lacks direct comparison to sibling operations.

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