Set the start and end times of a composition's work area to define the render region for previews and exports.
Set the work area (render region) start and end time of a composition
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | Work area end in seconds | |
| start | Yes | Work area start in seconds | |
| comp_name | Yes | Composition name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It indicates a mutation ('set') but does not mention whether an existing work area is overwritten, what happens if start or end is invalid, whether composition existence is required, or any side effects on the render queue.
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 a single, clear sentence with no filler. All necessary components—action, resource, and target—are present and front-loaded.
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 setter with fully documented parameters, the description is mostly adequate, but the lack of behavior context and usage guidance leaves gaps. Since there are no annotations and no output schema, a bit more detail about overwriting behavior or validation would improve completeness.
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 description coverage is 100%, so the baseline is 3. The description adds no parameter details beyond what the schema already explains; it only restates the concepts of start, end, and composition.
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 action ('Set'), the resource ('work area (render region)'), and the specific values ('start and end time') for a composition. This distinguishes it from sibling tools like ae_set_layer_time or ae_modify_composition, which target different resources or behaviors.
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 implies its use case: when someone needs to define the render/work area of a composition. However, it does not provide explicit guidance on when to prefer this tool over alternatives, nor does it mention prerequisites such as the composition already existing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.