start_automation

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

Annotations already indicate the tool is not read-only, not idempotent, and not destructive. The description adds specific behavioral context: it activates delivery, and returns errors if the automation is already sending or in draft status. This builds on annotations without contradicting them.

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 efficient with 6 sentences, starting with the main purpose, then usage guidance, parameter explanation, return format, and an example. No wasted words; front-loaded key information.

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 tool's moderate complexity and the presence of an output schema, the description fully covers prerequisites (obtain automation_id from list_automations), expected behavior, error conditions, and return format. The example solidifies understanding.

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 0%, so description must compensate. It provides a clear explanation for automation_id ('The automation workflow ID (e.g. 'auto123'). Obtain from list_automations.'), adding value beyond the schema's title and type. However, the optional account parameter is not described, leaving a gap.

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 'Start or resume' and the resource 'automation workflow', specifying the action 'activating delivery to queued subscribers'. It distinguishes itself from sibling tools like pause_automation and list_automations by mentioning them, 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?

Explicitly states when to use ('activate a new automation or resume a paused one') and provides alternatives: 'Use pause_automation to temporarily stop. Use list_automations to check current status.' This gives clear context for tool selection.

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