move_email

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

No annotations provided, so description carries full burden. It reveals that moving replaces all current mailbox assignments, which is key behavioral context. However, it does not mention authorization needs, rate limits, or what happens to previous assignments (e.g., whether the email is removed from all previous mailboxes).

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 short (two sentences plus Args list) and front-loaded with the main purpose. The Args section is structured but could be integrated into the prose to reduce length. Overall, efficient with no waste.

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 2 parameters, no enums, and an output schema existing, the description is adequate but has gaps. It lacks guidance on when to use this tool over bulk_move, does not mention error cases (e.g., invalid IDs), and does not elaborate on the effect on existing mailbox assignments beyond 'replaces all'.

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 description must add meaning. The Args section explains each parameter ('ID of the email' and 'Target mailbox ID'), but this is minimal—essentially restating the field names. No format hints or examples are provided.

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 an email to a different mailbox' and includes a clarifying note that it 'replaces all current mailbox assignments'. This distinguishes it from siblings like bulk_move by indicating it handles a single email.

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?

No explicit guidance on when to use this tool vs alternatives such as bulk_move for multiple emails. The usage is implied by the single-email parameter, but no when-not-to-use or alternative references are provided.

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