sendBulkMail

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

With no annotations, the description must carry behavioral disclosure, and it does add real value by stating that batching and rate limiting are automatic and that server limits are respected. However, it omits critical bulk-send semantics: whether one message is sent with many recipients or individual messages, what happens on partial failure, and permission requirements.

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?

Three short sentences, front-loaded with the core action and capability list. The final sentence ('Processes recipients in batches to avoid server limits') largely restates the 'automatic batching' already stated, so a small amount of redundancy exists.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the headline behavior adequately but leaves return shape, per-recipient error reporting, and partial-failure handling unaddressed, which an agent needs to invoke and interpret bulk sends correctly.

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 description coverage is 0% across 7 parameters, so the description must compensate. It covers the recipients, text, HTML, and attachments concepts, but leaves cc, bcc, and subject entirely unexplained, and gives no format guidance such as attachment encoding or address syntax.

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?

Specific verb+resource+scope: 'Send bulk emails to multiple recipients' clearly identifies the operation and differentiates itself from sendMail/sendHtmlMail via the 'bulk' framing. It stops short of naming the siblings it competes with, so it is clear but not fully disambiguating.

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?

Use for bulk/multi-recipient sending is implied by the description and the 'to' array, but there is no explicit statement of when to prefer this over sendMail, sendHtmlMail, or sendSimpleMail, and no exclusions such as message-count limits threshold.

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