Move Inbox Message

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

Annotations already convey destructiveHint=true and idempotentHint=true, but the description adds minimal behavioral context beyond the verb 'move'. It does not explain whether the source message is deleted, any side effects, or permission requirements, which are important for a destructive operation.

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 exceptionally concise: two sentences with no filler. It front-loads the core action and then provides a prerequisite, making it efficient for an agent to parse.

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 the tool has 6 parameters, 67% schema coverage, and an output schema (not shown), the description is brief. It misses behavioral details like return value or confirmation of move vs copy, and does not refer to the output schema. Adequate but with notable gaps.

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 67% (4 of 6 parameters have descriptions). The description adds marginal value by mapping 'system folder role' and 'custom folder ID' to parameters target_role and target_folder_id, but does not elaborate on formats or restrictions beyond the 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' and the resource 'one inbox message' to a 'system folder role or custom folder ID'. It differentiates from siblings like shipmail_delete_inbox_message and shipmail_update_inbox_message by specifying a move operation, though it does not explicitly contrast them.

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 provides explicit guidance to use shipmail_list_mailbox_folders first when targeting a custom folder, indicating a prerequisite. However, it does not specify when not to use this tool or mention alternative tools for similar tasks.

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