Microsoft 365 MCP Server

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

Excellent disclosure beyond annotations: explains the internal mechanics (creates new copy + removes original) which clarifies the destructive behavior declared in annotations. However, misses side effects like message ID changes, rate limits, or destination folder validation behavior.

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?

Two efficient sentences with zero waste. Front-loads the action, follows with implementation mechanics. Every word earns its place; no redundancy with title or annotations.

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?

Adequate for a destructive operation with nested parameters. Explains the atomicity semantics (copy-then-delete) which is critical for understanding data integrity. Does not need to explain return values (no output schema), though could mention error conditions or permission requirements.

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?

While schema coverage is 75%, the description adds crucial semantic context for the undocumented 'body.DestinationId' parameter by specifying 'another folder', indicating the destination is a folder reference. Could further clarify messageId format requirements.

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?

Crystal clear: specific verb (Move) + resource (message) + scope (within mailbox). Distinguishes from copy semantics by clarifying it creates a new copy AND removes the original, differentiating from other mail operations like delete or reply in the sibling list.

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?

No guidance on when to use this versus alternatives (e.g., delete-mail-message for permanent removal) or prerequisites (e.g., that messageId must be obtained first). No mention of user permissions or when to prefer move over other organization methods.

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