WAzion MCP Server

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

Since no annotations are provided, the description carries the full disclosure burden. It successfully indicates '[mutation]' status and explains bidirectional sync behavior (synchronizing archive/delete/spam actions). However, it omits safety details like idempotency, error handling, or side effects on existing synchronized data.

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 efficiently structured with a title-like opening, functional explanation of modes, and mutation tag. Minor redundancy exists between the em-dash separated title phrase and the main verb, but every sentence provides distinct information about the sync behavior.

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?

Given the simple 3-parameter schema with full coverage and no output schema, the description adequately covers the core functionality. However, as a mutation tool without annotations, it should ideally describe success indicators, return values, or potential error states to be fully complete.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the functional implications of the `sync_mode` values (what bidirectional synchronization actually does with server actions), providing semantic meaning beyond the enum labels.

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 it configures IMAP synchronization modes (inbox only vs bidirectional) for an email account, using specific verbs and resources. However, it lacks explicit differentiation from sibling tools like `update_email_account` or `update_email_folders`.

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 explains the functional difference between sync modes (bidirectional syncs archive/delete/spam actions), implying when to use each mode. However, it provides no explicit guidance on when to use this tool versus `update_email_account` or other email configuration alternatives.

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