Apply property updates to multiple After Effects layers simultaneously in a single transaction.
Apply property updates to multiple layers simultaneously in a single transaction
| Name | Required | Description | Default |
|---|---|---|---|
| updates | Yes | Array of layer property update operations | |
| compName | No | Composition name |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses one meaningful trait — all updates happen in a single transaction — but says nothing about rollback-on-failure behavior, partial failure handling, or required permissions, which is the critical unknown for a batch mutation tool.
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?
A single front-loaded sentence with no redundant or filler content. Every clause (verb, resource, batching, transaction) earns its place.
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 schema fully documents inputs and there is no output schema to explain, but for a destructive batch mutation with zero annotations the description should state failure/rollback semantics and the return shape. Those gaps leave the agent guessing about a transactional operation's edge cases.
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%, with each field and the nested properties object documented, so the baseline is 3. The description adds no parameter-level meaning beyond confirming batch semantics.
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?
States a specific verb ('Apply property updates'), resource ('layers'), and scope ('multiple layers simultaneously in a single transaction'). It implicitly distinguishes itself from the singular setLayerProperties sibling via 'multiple layers', but never names an alternative explicitly.
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?
No guidance on when to prefer this over setLayerProperties, or when batching is required. 'In a single transaction' hints at atomicity-driven use cases but the agent must infer that.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.