start_automation

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

With no annotations, the description fully discloses behavior: authentication via API key, rate limits (max 10 concurrent requests), respect for read-only/dry-run modes, and error cases (already sending, draft status). This is 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?

Well-organized: purpose, usage guidance, auth/rate limits, args, returns, example. Each sentence adds value; no fluff. Front-loaded with purpose.

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?

For a simple tool with one string parameter and output schema, description covers all critical aspects: authentication, rate limits, error states, and example. Complete without redundancy.

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% but description adds: 'The automation workflow ID (e.g. 'auto123'). Obtain from list_automations.' This gives example and source, adding meaning beyond schema. Could include more format details but sufficient.

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 explicitly states 'Start or resume all emails in an automation workflow, activating delivery to queued subscribers.' It uses specific verb (start/resume) and resource (automation workflow), and distinguishes from sibling tools like pause_automation and list_automations.

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 ('Use to activate a new automation or resume a paused one') and alternatives ('Use pause_automation to temporarily stop. Use list_automations to check current status'). Also mentions conditions like not when already sending or draft.

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