Send Test Email

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

The description reveals that the tool sends an email (mutating) and returns a messageId on success. Annotations indicate non-destructive and non-idempotent, and the description aligns, adding behavioral context beyond annotations.

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 concise (2 sentences) with the most important information front-loaded: action, return value, and usage guidance. No superfluous content.

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 simple test tool with an output schema and good annotations, the description covers all necessary aspects: purpose, return value, and when to use it.

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 covers 100% of parameters with descriptions. The description does not add additional meaning beyond the schema, so 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 tool's purpose ('Send a test email to verify SMTP is working') and distinguishes it from the sibling tool 'send_email' by recommending its use before relying on send_email in automated workflows.

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 explicitly advises to use this tool 'before relying on send_email in automated workflows,' which provides clear context and alternative. It could be improved by mentioning any prerequisites (e.g., SMTP configured), but the guidance is sufficient.

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