Zapmail MCP Server

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

No annotations are provided, so the description carries the full burden. It states the tool clears all cached data, implying a destructive operation, but doesn't disclose critical behavioral traits like whether this requires admin permissions, if it's reversible, potential performance impact, or rate limits. The description is minimal and misses key operational details for a mutation tool.

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, efficient sentence that front-loads the core action ('Clear all cached data') and follows with the purpose. There is no wasted verbiage, making it easy to parse and understand quickly.

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 tool's complexity as a destructive mutation with no annotations and no output schema, the description is incomplete. It lacks details on permissions, side effects, error conditions, and return values, which are essential for safe and effective use. The description does not compensate for the absence of structured data.

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%, with the single parameter 'confirm' documented as 'Confirmation required to clear cache.' The description adds no additional parameter semantics beyond this, such as explaining why confirmation is needed or providing examples. Baseline 3 is appropriate since the schema adequately covers the 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 action ('Clear all cached data') and the resource ('system cache'), with the purpose to 'free memory and ensure fresh data retrieval.' It distinguishes from siblings by focusing on cache management rather than domain, subscription, or mailbox operations, though it doesn't explicitly differentiate from tools like 'health_check' or 'get_server_info' that might involve system status.

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 guidance is provided on when to use this tool versus alternatives. The description mentions the outcome ('free memory and ensure fresh data retrieval') but doesn't specify scenarios, prerequisites, or exclusions, such as during high-load periods or after configuration changes. Without this, the agent lacks context for optimal invocation.

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