zoho_flag_emails

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description's "set or clear" correctly reflects the mutation-though-non-destructive nature, but adds nothing about permissions, idempotency, or what clearing a flag affects.

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 tightly written sentences with the verb front-loaded and the targeting constraint immediately following. No filler, nothing wasted.

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 6-parameter mutation tool with no output schema, the description covers targeting but leaves the folder-related parameters, the archive case, and the overlap with zoho_flag_threads unexplained. Adequate but with clear 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 coverage is only 50%, so the description should carry more weight. It usefully documents the messageId/threadId mutual exclusivity that the schema does not enforce, but says nothing about folderId, isArchive, or isFolderSpecific beyond what the schema already provides.

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 pair (set/clear) and resource (flag on emails), and distinguishes the two targeting modes. However it doesn't acknowledge the sibling zoho_flag_threads, which also flags threads, leaving some ambiguity about which tool owns the thread case.

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 parenthetical "give one of the two" gives implied usage guidance for messageId vs threadId, which is genuinely useful. But there is no when-to-use versus zoho_flag_threads or zoho_archive_emails, and no statement of prerequisites or 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.