Remove all keyframes from a layer property, or clear every animated property when no property is specified, to reset animation state in generative art projects.
Remove all keyframes from a layer property (or all properties if property omitted).
| Name | Required | Description | Default |
|---|---|---|---|
| layerId | Yes | ||
| property | No | Omit to clear all animated properties. |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears the full disclosure burden. "Remove all keyframes" does convey bulk destruction, but it says nothing about whether the change is undoable, what happens if the property has no keyframes, or what permissions/state are required — significant gaps for a destructive bulk operation.
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 sentence front-loads the action and the scope condition with zero filler. Nothing to trim.
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 two-parameter tool with no output schema the core behavior is adequately conveyed, but with zero annotations the description should have covered reversibility and no-op/error behavior for a destructive clear. Those omissions leave it merely adequate.
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 50%: `property` is already documented in the schema with the exact same "omit to clear all" semantics the description repeats, while `layerId` is undocumented in both places. The description adds little beyond restating structured content, so baseline 3 is appropriate.
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+resource ("Remove all keyframes") and a clear scope: per-property by default, all properties when omitted. That scope wording implicitly separates it from the singular sibling design_remove_keyframe, though no sibling is named outright.
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 parenthetical explains the omitted-property case, which is genuine usage guidance for the bulk path, but there is no explicit statement of when to use this versus design_remove_keyframe or a caution about when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.