Send Batch Emails

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool sends up to 100 transactional emails and implies batch behavior, but does not disclose potential side effects, partial failure handling, idempotency details, or rate limits. This is adequate but not rich.

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 tightly organized into three labeled sections (Purpose, NOT for, When to use) with no redundant words. Every sentence contributes to understanding the tool's purpose and usage boundaries.

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 schema's rich parameter descriptions and lack of output schema, the description adequately covers purpose, usage, and exclusions. It could be improved by mentioning idempotency or error behavior, but it is largely complete for a batch-email tool.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds a useful pointer that each item has the same fields as send-email, but it does not provide additional semantic detail beyond the schema for the idempotencyKey or email object fields.

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 up to 100 transactional emails in one API call,' with a specific verb, resource, and scope. It also distinguishes itself from siblings by noting that individual emails should use send-email and broadcasts should use create-broadcast + send-broadcast.

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 includes explicit 'NOT for' and 'When to use' sections, providing clear guidance on when to use this tool versus send-email or create-broadcast + send-broadcast. Examples (50 password resets, 100 receipts) further clarify appropriate use cases.

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