get_automation_emails

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

The description adds context beyond the annotations by stating 'Returns all emails regardless of status' and detailing the return structure. Given that annotations already declare readOnlyHint=true, the additional information about what data is returned is appropriate and helpful.

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 well-structured with a clear purpose sentence, usage notes, and an Args/Returns section. It is concise, using only a few sentences to convey all necessary information without extraneous content.

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 presence of an output schema that explains return values, and annotations covering safety, the description adequately covers purpose, usage, and parameter details. It is complete for a read-only list operation, though it could optionally mention error conditions or pagination.

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?

Although the schema description coverage is 0%, the description provides valuable semantics for the required automation_id parameter, including an example and source (list_automations). The optional account parameter is not mentioned, but its purpose is common and likely inferred from context.

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 'List' and the resource 'individual emails within an automation workflow', and includes specific details like sequence, delays, and send counts. It also distinguishes itself from sibling tools like get_email_activity and get_automation_email_queue, making the purpose unambiguous.

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?

The description explicitly warns not to confuse this tool with get_email_activity and advises using get_automation_email_queue for queued subscribers. This provides clear context for when to use each tool, though it does not cover all possible alternatives or edge cases.

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