setLayerKeyframe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure for a mutation tool. It does not say what happens to an existing keyframe at the same timestamp (overwrite vs. error), whether permissions are required, or how the keyframe interacts with later velocity edits. 'Optional interpolation' is the only behavioral hint offered.

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 well-formed sentence with the action front-loaded, no wasted clauses, and no repetition. It is appropriately sized, though it could carry one more sentence of behavior without becoming bloated.

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 is fully described and the core action is clear, but for a 7-parameter mutation tool with no annotations and no output schema, the definition leaves behavioral questions unanswered. Write semantics (overwrite behavior, error conditions) are the notable gap.

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 schema already documents all seven parameters, which sets the baseline at 3. The description adds 'at a specific timestamp' (time) and 'optional interpolation' (keyframeInterpolation), but these only echo existing field names rather than adding format or constraint detail.

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 and resource: 'Add a keyframe to a layer property at a specific timestamp'. The phrase 'layer property' implicitly separates it from setEffectPropertyKeyframe, which handles effect properties. However, it never names that sibling or any alternative, so differentiation is left to inference.

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?

There is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as setEffectPropertyKeyframe or setKeyframeVelocity. The 'layer property' wording hints at scope but stops short of telling an agent when this tool is the right choice.

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