notification-testEmailConnection

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

The description provides no behavioral information. Annotations indicate idempotentHint=true and openWorldHint=true, but the description does not leverage or add to these. It doesn't mention side effects, permissions, or response 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 extremely short, but it is underspecified to the point of uselessness. While brevity is valued, this lacks essential content; it is not 'appropriately sized' for the tool's complexity.

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?

With 6 required parameters, no output schema, and no param descriptions, the description is severely incomplete. It fails to inform the AI about parameter formats, return values, or any contextual details needed for correct invocation.

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 0%, yet the description offers no parameter explanations. The six required parameters (smtpServer, smtpPort, username, password, toAddresses, fromAddress) are left entirely for the AI to infer from names alone.

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 is 'POST /notification.testEmailConnection', which merely restates the tool name and HTTP method. It does not specify what the tool does beyond the implied HTTP POST action, offering no clear verb or resource description.

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 on when or how to use this tool. No alternatives, prerequisites, or context provided. The sibling tools include many notification-test* variants, but the description doesn't differentiate them.

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