outlook_move_message

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

The description explicitly states 'removes from source', making the destructive nature of the operation clear, which is not fully captured by the annotations (destructiveHint: false). This transparency helps the agent understand the side effect of moving.

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, with two sentences: the first states the purpose and effect, the second provides usage alternatives and parameter details. No redundant information, well-structured.

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?

The description covers the core purpose, effect, alternatives, and parameter behavior. No output schema is provided, but the tool's return is not complex. The description is sufficient for an agent to decide when and how to use this 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?

The folder parameter is well explained (display names, well-known names, Graph IDs, prefer names), adding value beyond the schema. The message_id parameter is not described but is self-explanatory as a message identifier. Since schema coverage is 0%, the description compensates for one of two parameters adequately.

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 verb 'Move' and the resource 'message', and explicitly distinguishes from copy and delete operations. It also clarifies that moving removes the message from the source folder, making the purpose unambiguous.

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?

Provides explicit guidance on when to use sibling tools: use outlook_copy_message for duplication, outlook_delete_message for deletion, and warns against using move to 'deleteditems' as a deletion method. Also explains the folder parameter accepts display names, well-known names, or Graph IDs, with a preference for names.

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