zoho_move_emails

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the mutation/open-world profile is already covered. The description adds the mutual-exclusion constraint, but says nothing about what happens to the source folder, whether the move is reversible, or permission/rate-limit requirements for a write operation.

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, front-loaded with the action and then the targeting rule. No filler.

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?

No output schema, so the description carries return-value burden too. It covers the key targeting choice but omits the semantics of isArchive, isFolderSpecific/folderId, and the required destfolderId, leaving real gaps for a 6-parameter mutation tool.

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 67%, so much parameter meaning comes from the schema. The description adds genuine value by stating messageId and threadId are mutually exclusive (the schema does not enforce oneOf), but it never explains folderId, destfolderId beyond its name, isArchive, or isFolderSpecific.

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 ('Move emails to another folder') and clarifies scope (individual messages vs whole threads). However, it doesn't distinguish itself from the sibling zoho_move_threads, which overlaps with the threadId path described here, leaving an agent to guess which tool to pick for conversations.

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 gives parameter-selection guidance ('give one of the two'), which is useful, but offers no when-to-use guidance relative to siblings like zoho_move_threads, zoho_archive_emails, or zoho_delete_email. Usage is implied rather than stated.

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