mailplus_move_messages

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

With no annotations, the description must disclose all behavioral traits. It only reveals the confirmation requirement, but omits important details such as whether the move is a copy+delete, whether the destination folder must exist, permissions needed, rate limits, or error handling. This is insufficient for safe agent selection.

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 two sentences, front-loading the action in the first sentence and a key constraint in the second. No wasted words; every sentence earns its place.

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 4 parameters, no output schema, and no annotations, the description is too sparse. It does not cover return values, prerequisites (e.g., folder existence), error states, or behavioral details beyond the confirmation flag. Critical missing context for a state-changing operation.

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 input schema has 50% description coverage; two parameters (dest_folder, account) have descriptions, but message_ids and confirm do not. The description adds value only to confirm by stating it must be true for execution. No additional semantics are provided for other parameters, so the description only modestly compensates for the schema gap.

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 'MailPlus messages to another folder,' which is specific and distinguishes it from sibling tools like mailplus_get_message or mailplus_mark_messages. The addition of the confirm requirement adds precision.

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 includes the critical usage condition 'Requires confirm=true to execute,' but it does not provide guidance on when to use this tool vs. alternatives, such as other mailplus operations or when to avoid it. No explicit exclusions or alternative tools are mentioned.

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