move_message

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say whether the destination folder must already exist, whether moving requires permissions, what happens on invalid IDs, or what the response looks like.

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?

A single tightly-worded sentence that front-loads the action and resource with zero waste. The parenthetical parameter hints are efficient rather than verbose.

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?

With no annotations, no output schema, and 0% schema description coverage, the description needs to do more. It covers the basic action and parameter formats but omits error behavior, folder prerequisites, and return semantics for a simple two-parameter mutation.

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 0%, so the description must compensate and does so partially: it clarifies message_id accepts a ref or raw id and destination_folder accepts an id or well-known name. That adds real meaning beyond the bare schema, but the accepted formats/values are not fully specified.

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 states a specific verb (move) and resource (message) plus the destination concept (folder). It is clear what the tool does, though it does not explicitly name a sibling like bulk_move_messages to distinguish the single-message case.

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?

Usage is only implied by the singular 'a message', which suggests it is for one message rather than bulk operations. It never states when to use this instead of bulk_move_messages or archive_message, leaving the agent to infer the single-vs-bulk distinction.

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