emails_batch_create

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

With no annotations, the description carries full burden but only states it creates records without behavioral details. It doesn't disclose whether this sends emails, saves drafts, requires authentication, has rate limits, returns created IDs, or handles errors. For a mutation tool with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the core functionality without unnecessary elaboration.

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 complex batch creation tool with 1 parameter (but deeply nested), 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'email records' are, how they relate to sending emails, what the tool returns, or any behavioral constraints, leaving critical gaps for the agent.

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%, and the description provides no parameter information. It doesn't explain the 'inputs' array structure, required fields like 'hs_email_subject', or the complex nested objects for properties and associations. The description fails to compensate for the schema's lack of descriptions.

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 verb ('Create') and resource ('multiple email records'), specifying it's a batch operation ('in a single request'). It distinguishes from non-batch siblings like 'emails_create', but doesn't explicitly contrast with other batch tools like 'emails_batch_update' or 'emails_batch_read'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or compare with single-create ('emails_create') or other batch operations. The agent must infer usage from the name alone.

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