get_automation_emails

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

Describes read-only nature, safe to retry, and returns all statuses. Without annotations, it covers key behavioral traits. Could explicitly state no side effects.

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?

Concise with no wasted words. Front-loaded main purpose, then clarifications, then behavioral notes, then parameter details in a structured format.

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 simple tool (1 param, no enums, has output schema), the description fully covers parameter explanation and return summary. Completes all needed context.

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 0%, but description adds an example ('auto123') and source (list_automations) for the single parameter, adding significant value beyond schema.

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 verb 'list' and resource 'emails within an automation workflow'. Differentiates from siblings like 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 to use (list emails in automation) and when not (not campaign engagement). Provides alternative tools and usage context (authentication, concurrency limits, read-only).

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