Move emails

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true. The description adds genuinely useful context beyond that: "this extension never permanently deletes anything" reassures the agent that the trash destination is safe, and it discloses the only deletion pathway. It stops short of describing partial-failure behavior for large batch moves.

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?

Two tight sentences with the core action front-loaded and the deletion-safety caveat immediately after. No filler or 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?

Safety profile comes from annotations and all parameter semantics come from the schema, so the description covers the essentials for a mutation tool. It says nothing about what happens when a move fails for some of up to 200 ids, which an agent invoking a batch mutation would benefit from knowing.

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 100%, so the schema already documents ids, folder, account and destination. The description's destination examples duplicate the schema's own enumeration rather than adding format or constraint details, so baseline 3 applies.

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?

States a specific verb and resource ("Moves messages to another folder") and gives concrete destination examples ("archive", "trash", "spam", "inbox"). It does not explicitly distinguish itself from the sibling update_emails, which also mutates messages, so it falls short of a 5.

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 implies a usage scenario by explaining that deleting is accomplished via moving to Trash, which tells the agent when this tool substitutes for a delete operation. However, it names no alternatives and gives no explicit when-not guidance relative to update_emails.

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