zoho_mark_threads_unread

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, lowering the bar, but the description adds nothing beyond the title: it does not say whether read flags are cleared, whether the operation is idempotent, or how folder-scoped vs. archive targeting behaves.

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?

A single front-loaded fragment with zero waste. It is appropriately sized for its content, though the extreme brevity reflects under-specification rather than disciplined conciseness.

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 4-parameter mutation with no output schema, the description omits the meaningful behaviors an agent needs: how threadId arrays are processed, what isArchive and isFolderSpecific do in combination, and when to prefer this over the read/email-level variants.

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 75%, with folderId, threadId, and isArchive/isFolderSpecific documented inline (including the 64-bit string-ID caution and the folderId dependency). The description contributes no parameter meaning at all, so the baseline 3 applies rather than higher.

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 ('mark ... as unread') and the scope qualifier 'whole threads', which distinguishes it from the email-level sibling zoho_mark_emails_unread. It does not, however, explicitly name or contrast with the nearest alternatives (zoho_mark_emails_unread, zoho_mark_threads_read).

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 guidance on when to use this tool versus zoho_mark_emails_unread for single messages, or versus zoho_mark_threads_read. No prerequisites, batch limits, or exclusions are mentioned.

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