zoho_move_threads

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — it does not say whether the thread is removed from the source folder, whether archive state is preserved, or what happens on partial failure across multiple threadIds.

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?

One front-loaded sentence with zero filler. It is efficient, though arguably too terse for a 5-parameter mutation tool, since a second sentence on threading/archival behavior would have earned its place.

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?

For a 5-parameter, multi-ID mutation with no output schema and no annotations explaining semantics, the description omits the isArchive and isFolderSpecific/folderId interaction entirely. An agent must infer required combinations from the schema alone, which leaves notable gaps.

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 80%, so the schema itself documents folderId, threadId, destfolderId, isArchive, and isFolderSpecific with useful notes about string-encoded 64-bit IDs. The description adds no parameter meaning at all, so the 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 ('Move') and resource ('whole threads') with the destination ('another folder'), which is enough to separate it from zoho_move_emails (emails) and zoho_flag_threads. It does not explicitly name the sibling alternative, so it stops 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?

There is no when-to-use guidance, no mention of prerequisites (e.g. destination folder must exist, IDs from zoho_list_folders), and no distinction from zoho_move_emails or zoho_archive_emails beyond the word 'threads'.

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