list_automations

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

Discloses authentication via API key, max 10 concurrent requests, and that it is read-only and safe to retry. Also describes the return format, providing full transparency beyond the missing annotations.

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?

Well-organized in paragraphs: purpose and behavior, authentication/limits, parameter details, return format. Every sentence adds value; no fluff.

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?

With an output schema present, the description still details the return JSON structure (total_items, automations array with fields), making it complete for a paginated list tool.

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?

The Args section explains count (range 1-1000, default 20) and offset (pagination usage), adding meaning beyond the schema which had no descriptions (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?

Description clearly states the verb 'List' and resource 'automation workflows', specifies included fields like status and send counts, and differentiates from sibling tools like get_automation_emails.

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 says it returns all automations regardless of status, ordered by creation date descending, includes both Classic Automations and Customer Journeys, and advises using get_automation_emails for individual emails.

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