list_automations

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

Discloses ordering by creation date descending, exclusion of Journeys due to API limitations, and return structure. Adds significant context beyond annotations (readOnlyHint=true) without contradiction.

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?

Efficiently front-loaded with purpose, then scope clarification, alternatives, concise Args, and Returns section. Every sentence adds value without 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?

Comprehensive: explains ordering, API limitations, alternatives, pagination, and return JSON shape with key fields. Sufficient for a list tool with output schema.

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?

Adds meaning for count (range and default) and offset (pagination usage) via Args section, compensating for 0% schema coverage. However, the 'account' parameter is not described, leaving one parameter undocumented.

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 Classic Automation workflows, including status and send counts. Explicitly distinguishes from Customer Journeys and siblings like get_automation_emails and search_automation_campaigns.

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?

Provides explicit when-to-use (Classic Automations) and when-not-to-use (Customer Journeys) with clear alternatives: search_automation_campaigns, get_automation_emails, get_automation_summary.

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