move-mail-message

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

The description discloses that the original message is removed, aligning with destructiveHint annotation. It adds context about destinationId well-known names but does not cover permissions or failure modes.

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 lines and a tip, front-loaded with the action, and no unnecessary words.

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 no output schema, the description adequately covers the operation but could mention the response type (e.g., the moved message object). Annotations compensate slightly for missing details.

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 description adds significant value for the body parameter by listing well-known folder names, beyond the schema. Other parameters lack additional context, but schema coverage is high.

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 distinguishes from copying by noting the original is removed. The tip adds clarity on destinationId values.

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 implies usage (move vs. copy) but does not explicitly state when to use this tool or provide exclusions or alternatives besides the tip.

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