update_email_sync

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

The description discloses that it mutates sync mode and lists the two options. However, with no annotations, it does not cover side effects, required permissions, or what happens to existing sync state. The '[mutation]' tag adds some awareness but lacks detail.

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?

The description is a single, well-structured sentence that conveys the purpose and options without any unnecessary words. It is front-loaded and efficient.

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 simple update tool with no output schema, the description is adequate. It explains the core action and parameter values. Missing details like error scenarios or prerequisites are minor given the tool's simplicity.

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 100% with descriptions, but the description adds explanatory context for 'bidirectional' (syncs archive, delete, spam). This goes beyond schema enum values, providing clearer semantics for the sync_mode parameter.

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?

The description clearly states the tool updates IMAP sync mode for an email account, specifying the two possible modes (inbox only or bidirectional). It distinguishes itself from sibling tools like 'update_email_account' by focusing solely on sync configuration.

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 implies usage when changing sync mode but does not explicitly state when to use it vs alternatives like 'force_email_sync' or 'update_email_account'. No when-not-to-use or prerequisites are mentioned.

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