move_email

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

Discloses key behaviors like dry_run preview, only_read skipping unread, and message_ids overriding filters. Mentions a safety limit (max_moves=50). However, with no annotations, it lacks details on irreversibility, permissions, or error states that a mutation tool should declare.

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?

Front-loaded with a one-line purpose, followed by useful usage tips and a well-organized parameter list. Slightly long but every part adds value, with no wasted sentences.

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 11 parameters and no annotations, the description covers most aspects: filtering, preview, archiving, exact IDs. Mentions return value briefly. Lacks clarification on overlap between subject_keyword and subject_keywords, but otherwise complete.

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 fully documents all 11 parameters. The Args section adds clear purpose, defaults, and usage examples (e.g., nested mailboxes with '/'), going well beyond schema names and types.

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 'Move email(s) matching filters from one mailbox to another', using specific verbs and resources. It distinguishes from siblings by mentioning a special path similar to update_email_status and providing archiving guidance.

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 usage tips (dry_run, only_read, archiving) and explains message_ids for precise targeting. However, it does not explicitly state when to use this tool versus siblings like search_emails or export_emails, nor does it list exclusions or prerequisites.

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