move-mail-message

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

The description goes beyond annotations (destructiveHint=true) by detailing the exact behavior: creates a copy in destination and removes the original. It discloses that the operation is destructive and explains the two-step process. No contradictions with annotations.

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 only two sentences. The first sentence states the purpose and effect concisely. The second sentence adds a clear, helpful tip. No unnecessary words, front-loaded information.

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 tool with 4 parameters, no output schema, and annotations, the description covers the main action and a key parameter nuance. It misses some context like required permissions or that the destination folder must exist, but it is mostly complete given the 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?

Schema coverage is 75%, so baseline is 3. The description adds valuable semantics by explaining that 'destinationId accepts folder ID or well-known name' with examples, which is not in the schema. This enriches parameter understanding beyond the structured schema.

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 action 'Move a message to another folder within the specified user's mailbox', which is a specific verb+resource combination. It distinguishes itself from sibling tools like copy-mail-message (which leaves original) and delete-mail-message (which removes without copy).

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 the effect 'creates a new copy... and removes the original', providing context for when to use this tool (move) vs alternatives (copy, delete). However, it does not explicitly state when not to use or compare with siblings, but the tip about destinationId adds practical guidance.

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