create_automation

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

With no annotations, the description carries full burden. It discloses the draft nature, one-time entry constraint, and free drafting. However, it does not mention permissions, rate limits, or error handling. The behavioral details are adequate but could be more comprehensive.

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 concise, using a single paragraph that front-loads the main purpose. Every sentence provides relevant information 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?

Given the complexity (6 params, nested objects, no output schema), the description explains the triggering and steps thoroughly. However, it lacks mention of the return value, which would be helpful for an agent to understand what to expect after creation.

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 100%, but the description adds value by clarifying the structure of 'trigger' (one of three types) and 'steps' (1-20 items of specific types), and explains the XOR condition for email steps and 'approvalRequired' default. This goes beyond the schema descriptions.

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 that the tool creates an automation DRAFT, not an active automation, and uses the specific verb 'Create' along with resource 'automation DRAFT'. It distinguishes from siblings like 'activate_automation' and 'update_automation' by emphasizing the draft state.

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 explains that the automation runs nothing until activated, implying usage before activation. It also notes that drafting is free on every plan and that a contact enters each automation at most once, providing guidance on when to use this tool and its constraints. However, it does not explicitly state when not to use it.

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