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 what the tool does but lacks behavioral details such as whether it's read-only or has side effects, if it requires specific permissions, potential performance impact, or what the output format might be. For a diagnostic tool with no annotations, this leaves significant gaps in understanding its behavior.

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 efficiently conveys the tool's purpose and scope without unnecessary words. It is front-loaded with the main action and includes key components, making it easy to understand at a glance.

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 (a diagnostic operation with one parameter) and the absence of annotations and output schema, the description is adequate but incomplete. It covers the 'what' but lacks details on behavior, output, or usage context, which are important for a health check tool. It meets minimum viability but has 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 description coverage is 100%, with one parameter ('detailed') fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as examples of what 'detailed' health information includes. With high schema coverage, the baseline score of 3 is appropriate.

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 specific action ('Perform a comprehensive health check') and the target resource ('MCP server'), with explicit components listed ('API connectivity, cache status, and configuration validation'). It distinguishes itself from all sibling tools, which are focused on domains, mailboxes, subscriptions, etc., making this a unique diagnostic tool.

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 for system diagnostics but does not explicitly state when to use this tool versus alternatives. It mentions 'comprehensive health check' which suggests it's for overall system status, but there is no guidance on prerequisites, frequency, or specific scenarios (e.g., troubleshooting vs. routine checks).

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