test_smtp_config

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

With no annotations provided, the description takes on the responsibility of disclosing side effects. It explicitly states 'without modifying the server configuration', which is a key behavioral trait that assures the tool is non-destructive. It could further explain what the test actually does (e.g., sends a probe email or only checks authentication) but the core safety guarantee is clear.

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 concise sentence, front-loaded with the verb 'Test'. It conveys the tool's purpose and a critical constraint in minimal words. There is no redundancy or filler, making it 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?

The tool is relatively simple with fully documented parameters and a clear purpose. The only notable gap is the absence of an output schema and any description of return values, which could leave the agent uncertain about what success/failure looks like. However, the name and description imply a test result, and the overall context is sufficient for 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?

The input schema has 100% description coverage for all 5 parameters, so the baseline is 3. The description adds little extra parameter meaning beyond referring to 'custom credentials', which maps loosely to user/password but does not clarify details like secure's default behavior. The schema adequately covers semantics.

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 identifies the tool's action ('Test'), the resource ('SMTP configuration'), and a specific scope ('with custom credentials without modifying the server configuration'). This distinguishes it from sibling tools like send_email or verify_connection by emphasizing the no-side-effect testing aspect.

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 a usage context: testing SMTP settings using custom credentials without altering the server. However, it does not explicitly state when to prefer this over alternatives like verify_connection, nor does it provide any 'when not to use' guidance. The usage is inferred rather than explicit.

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