create_automation

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

No annotations provided, so description bears full burden. It discloses that duration=0 creates a step and duration>0 creates a linear ramp, adding value beyond schema. Missing details like whether it replaces existing automation or appends.

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 with three sentences and an example, front-loading the main purpose. Every sentence adds value with no wasted words.

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?

The description covers points structure and duration behavior, but does not mention output, error conditions, or prerequisites (e.g., device must exist). Given 5 parameters and the presence of an output schema, more context is needed.

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 the description only explains the 'points' parameter (structure and duration meaning). The other four parameters (track_index, slot_index, device_index, parameter_index) are left undocumented, so description only partially compensates for low coverage.

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 'Create automation for a device parameter in a clip' with a specific verb, resource, and context. It distinguishes from sibling tools like 'automate_mixer' and 'add_automation_points'.

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 the points structure and provides an example, implying when to use. However, it does not explicitly state when not to use or compare to alternatives like 'add_automation_points'.

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