send-serial-email

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

No annotations were provided, but the description fully covers behavioral traits: it SENDS many real emails immediately, cannot be unsent, requires explicit user confirmation, and returns a per-recipient report. This compensates for the lack of 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, with three short paragraphs that are front-loaded with the core use case. Every sentence adds value, no redundancy or fluff.

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 (mail merge with placeholders, safety concerns) and the presence of an output schema (referenced but not shown), the description is complete: it covers when to use, safety, return format, and distinguishes from alternatives. Little else is needed.

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 coverage is 100%, so baseline is 3. The description adds context by explaining placeholder syntax {{Key}}, default and max delayMs, and the structure of recipient variables. It integrates parameter usage into the overall workflow, providing value beyond the schema.

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 explicitly states it is for mail-merge with personalized copies to many recipients, using {{Key}} placeholders. It clearly distinguishes from send-email (shared list) and create-draft (saving for review).

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 explicit 'Use when' and 'Do not use when' conditions, naming specific alternative tools (send-email, create-draft). It also gives safety prerequisites, requiring explicit user confirmation.

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