verify_connection

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

With no annotations provided, the description is the sole source of behavioral context. It states that the tool 'verifies' the connection and authentication, implying a read-only test, but does not explicitly confirm it is non-destructive, describe any side effects, or explain what happens on success or failure. The term 'verify' is suggestive but does not fully disclose 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, focused sentence that immediately states the tool's purpose. It wastes no words and is easy to parse.

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 zero-parameter tool with no output schema, the description covers the core functionality but leaves some contextual gaps. Specifically, it doesn't clarify how 'verify_connection' differs from the sibling tool 'test_smtp_config,' and it doesn't specify the result format or any preconditions. This is enough for basic understanding but not fully complete for an AI to select with confidence.

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 takes zero parameters, so the schema is trivially covered at 100%. The description does not need to add parameter details, and it correctly avoids inventing any. A baseline score of 4 is warranted given the absence of parameters.

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 uses the verb 'verify' with a clear resource ('SMTP connection and authentication') and references 'configured credentials,' making the tool's function apparent. However, it does not distinguish itself from the sibling 'test_smtp_config,' which likely serves a similar purpose, so it stops short of a 5.

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 no guidance on when to use this tool versus alternatives like test_smtp_config or send_email. There is no mention of preferred scenarios, prerequisites, or exclusions, leaving the agent to infer selection.

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