move_email

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

The description discloses key behaviors: subject keyword matching, nesting separator for mailboxes, safety limit (max_moves default=1), and that message_ids overrides subject filtering. No annotations exist, so description carries the burden well.

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 front-loaded with a clear action sentence, followed by structured Args and Returns. It is moderately sized and fairly concise, though could trim some redundancy.

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 6 parameters, no annotations, and many siblings, the description covers core behaviors but lacks usage guidelines and comparison to similar tools. It explains override logic but doesn't address common workflows.

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?

With 0% schema description coverage, the Args section provides complete parameter explanations, including defaults, nesting hints, and the override relationship between message_ids and subject_keyword. This adds significant meaning 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 email(s) matching a subject keyword from one mailbox to another.' This is specific and differentiates from siblings like 'bulk_move_emails' and 'imap_bulk_move'.

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 guidance on when to use this tool versus alternatives like 'delete_emails', 'archive_emails', or 'bulk_move_emails'. The description doesn't mention prerequisites or conditions for use.

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