Move Email Folder

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

The description adds value beyond annotations by noting user confirmation is recommended and clarifying the move operation's effect. Annotations already indicate non-destructive and idempotent behavior, but the description doesn't contradict them.

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 concise, front-loaded with a summary, and uses a structured Args list. Every sentence adds value without unnecessary fluff.

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?

The description covers purpose, parameters, return value, and a safety note. It lacks details on permissions, error handling beyond ValueError, or integration with sibling tools like emailfolders_get_tree, but is adequate given the output schema.

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 description provides clear, helpful explanations for each parameter (folder_id, destination_folder_id, account_id), significantly adding meaning beyond the schema's type and required attributes.

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 a mail folder to a different parent') and the resource ('mail folder'), distinguishing it from sibling tools like emailfolders_rename or emailfolders_delete.

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 mentions user confirmation recommendation but provides no explicit guidance on when to use this tool versus alternatives (e.g., emailfolders_delete, emailfolders_empty), nor when not to use it.

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