Zapmail MCP Server

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

With no annotations provided, the description carries full burden but only minimally discloses behavior. It mentions the server will 'plan steps and optionally execute them' but doesn't describe what planning entails, what types of steps might be generated, whether execution is reversible, what permissions are needed, or what happens when execution fails.

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 perfectly concise with two sentences that each earn their place: the first establishes the core functionality with an example, the second explains the dual planning/execution capability. No wasted words, front-loaded with the main purpose.

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 complex planning/execution tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the planning output looks like, what types of operations can be planned, whether execution requires confirmation, or how errors are handled during multi-step execution.

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 100%, so the schema already documents all 4 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, maintaining the baseline score of 3 for high schema coverage.

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's purpose with a specific verb ('plan steps and optionally execute them') and resource ('natural language instruction'), and distinguishes it from all sibling tools which are specific domain/mailbox/workspace operations rather than a high-level planning interface.

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 provides clear context about when to use this tool ('Give a natural language instruction') and implies it's for complex multi-step tasks, but doesn't explicitly state when NOT to use it or name specific alternative tools for simpler operations.

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