move_messages

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

Even with annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description adds significant behavioral insight: error on missing folder, short IDs becoming invalid after moving, a 25-message limit, and a user confirmation requirement. No contradiction 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 tightly structured: a one-line purpose, bullet-style behavioral notes, and a clear Args section. Every sentence provides actionable information with no redundancy or filler.

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 only two parameters and an output schema, the description covers error conditions, prerequisites, side effects, limits, and parameter formats. It leaves nothing essential unexplained for an agent to invoke it correctly.

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 description coverage is 0%, so the description carries full responsibility for parameter semantics. It explains message_ids format with examples (#1,#2,#5) and max count, and folder with examples ('領収書', '受信トレイ/請求'). This adds substantial meaning beyond the bare 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 opens with 'メールを指定フォルダへ移動する' (Moves emails to the specified folder), which is a specific verb+resource+destination statement. It clearly distinguishes from sibling tools like move_folder, archive_messages, and move_to_trash by emphasizing arbitrary folder targeting.

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?

Provides clear context: call create_folder if the destination doesn't exist, confirm with user before bulk moves, and re-run search_messages because IDs become invalid. However, it does not explicitly state when not to use this tool in favor of alternatives like move_by_search or archive_messages, though the parameter difference implies it.

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