zoho_mark_threads_read

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

Annotations establish this is a mutating (readOnlyHint=false) but non-destructive operation; the description adds nothing beyond a restatement of the name. It doesn't explain the folder-scoping / archive interaction implied by isFolderSpecific and isArchive, nor that the action is irreversible for read-state purposes.

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 short, front-loaded sentence with zero padding, but its brevity stems from under-specification rather than efficiency given the tool has four parameters and mutation semantics to convey.

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 four-parameter mutation tool with no output schema and no indication of return values, side effects, or the archive/folder-mode interaction, one sentence is insufficient. An agent cannot tell from the description how batch thread marking behaves or what happens on partial failure.

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 the schema itself carrying useful detail such as the 64-bit string-precision warning and the folderId requirement when isFolderSpecific is true. The description contributes no additional parameter meaning, so the baseline of 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 (mark), resource (whole threads), and resulting state (as read). The word 'threads' vs. 'emails' implicitly distinguishes it from sibling zoho_mark_emails_read, though it never names the sibling explicitly.

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?

No when-to-use guidance, no prerequisites, and no mention of when to prefer this over zoho_mark_emails_read or zoho_mark_threads_unread. The agent must infer the thread-vs-email choice purely from the tool name.

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