setLayerKeyframes

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It states that the tool sets multiple keyframes but does not mention whether existing keyframes are overwritten, what the call returns, required permissions, or error behavior. For a mutation operation, this is a significant gap.

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 two short sentences, front-loaded with the core purpose, and contains no redundant information. It is appropriately sized for the tool's simplicity.

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?

Despite having no output schema and no annotations, the description does not explain the effect of setting keyframes (e.g., replacement behavior), return values, or error cases. It also does not distinguish from setEffectKeyframes, which is a related sibling. The description is too thin for a tool that mutates layer state.

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 100% (all properties have descriptions), so the baseline is 3. The description adds no extra semantic context beyond what the schema already provides; it merely repeats that multiple keyframes are set.

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 ('Set') and resource ('multiple keyframes') and explicitly differentiates from the singular sibling tool setLayerKeyframe by highlighting batch efficiency. This makes the purpose unambiguous and distinguishes it from the main alternative.

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?

It explicitly says this is more efficient than repeated setLayerKeyframe calls, which tells the agent when to use this tool instead of the singular version. This is an explicit usage guideline with a named alternative.

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