get_automation_emails

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

Describes authentication (API key), concurrency limit (max 10), and idempotency (read-only, safe to retry). Since annotations are absent, this fully covers behavioral traits.

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?

Information is front-loaded and well-structured, but could be slightly more concise. All sentences are valuable.

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 simple input (1 param, no nested objects) and output schema mentioned, the description fully explains purpose, usage, parameters, and return structure.

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?

Provides format and source for automation_id ('e.g. 'auto123'. Obtain from list_automations'), which is not in the schema (0% coverage).

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?

Clearly states it lists individual emails in an automation workflow with sequence, delays, and send counts. Differentiates from get_email_activity and get_automation_email_queue.

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?

Explicitly tells when not to use (confusing with campaign engagement) and directs to get_automation_email_queue for queued subscribers. Also notes how to obtain automation_id.

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