sendcraft_batch_send

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

No annotations are present, so the description must carry the burden. It discloses the 100-email limit and that emails can have different fields, but does not mention partial failure behavior, rate limits, or response format, leaving behavioral uncertainty.

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?

Two sentences, front-loaded with the core capability, no redundant information. Every sentence adds value.

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 batch-send tool, the description covers the essential capability and limit. However, with no output schema and no mention of return values or failure semantics, it leaves some gaps for a tool of this complexity.

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% with the 'emails' array described. The description adds minimal meaning beyond the schema, only clarifying that each email can have different recipient, subject, and body, which is already implicit in the schema structure.

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?

Description clearly states the tool 'Send up to 100 distinct emails in a single API call', uses the verb 'Send' with resource 'emails', and explicitly contrasts with send_email, distinguishing it from the sibling tool.

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?

It explicitly notes this is more efficient than calling send_email 100 times, implying use for batch sending distinct emails. However, it does not mention cases where it should not be used (e.g., sending the same email to many recipients) or provide alternatives like campaigns.

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