list_automations

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

Despite no annotations, the description fully discloses behavior: returns all automations (no filtering), order, inclusion of both automation types, read-only nature, retry safety, concurrency limit, and auth method.

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 and well-structured: front-loaded main purpose, then details, then structured Args/Returns. Every sentence adds value with no redundancy.

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 it's a list tool with output schema, the description fully specifies return shape (total_items and automations array with fields). Distinguishes from sibling automation tools. No gaps.

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?

With 0% schema description coverage, the description adds all needed meaning: parameter ranges (1-1000 for count), defaults, and pagination usage hint for offset. Schema only provides basic types.

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 'List automation workflows' and specifies it returns all automations regardless of status, ordered by creation date descending, covering both Classic Automations and Customer Journeys. It distinguishes from 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 when to use this tool vs. alternatives: 'Use get_automation_emails for individual emails within a workflow.' Also provides authentication, concurrency limit, and safety info.

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