MCP Email Service

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it has side effects, what the response format might be, or any error conditions. The single phrase 'Check connection' provides zero behavioral context.

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?

While technically concise with only two words, this represents under-specification rather than effective brevity. The description fails to provide necessary context about what's being checked or why, making it inefficient despite its short length. Every word should earn its place, but these two words don't provide sufficient value.

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 complexity of a connection-checking tool in an email-focused server with no annotations and no output schema, the description is completely inadequate. It doesn't explain what system is being checked, what constitutes a successful connection, what information is returned, or how this tool relates to the email operations performed by sibling tools.

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?

The tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters since none exist, and it doesn't attempt to describe non-existent parameters. This is appropriate for a parameterless tool.

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 'Check connection' is a tautology that merely restates the tool name without specifying what resource or system is being checked. It doesn't distinguish this tool from its siblings, which all operate on emails. The description fails to clarify whether this checks database connectivity, API status, or email server availability.

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 absolutely no guidance about when to use this tool versus alternatives. Given the sibling tools all handle email operations, there's no indication whether this should be used before other operations, as a health check, or in what context. No prerequisites, alternatives, or exclusions are mentioned.

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