clear_keyframes

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

No annotations are provided, so the description carries the full burden. It does disclose the meaningful side effect (animation on the property is turned off), which is genuinely useful context, but it omits that the operation is bulk and irreversible (no undo guidance, no partial-failure behavior) for a destructive mutation.

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 short sentence, front-loaded with the action and resource, with the outcome in parentheses. Nothing wasted and nothing buried.

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 five-required-parameter destructive mutation with no annotations and no output schema, the description is thin: it never says keyframes cannot be restored, whether other properties are affected, or how to verify the result (e.g. via get_keyframes). The schema compensates for parameter detail but not for behavioral risk.

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 parameter documented including lookup hints (get_clip_effects, get_timeline_clips) and a trackType enum. The description adds nothing about the five required parameters, so baseline 3 applies.

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 ('Remove') and resource ('all keyframes from a property') and adds the consequence '(turns animation off)'. The word 'all' implicitly contrasts with the single-keyframe sibling remove_keyframe, though that sibling is never named.

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?

Usage is only implied through 'all' — an agent can infer this is the bulk alternative to remove_keyframe, but the description never states when to pick this over remove_keyframe or get_keyframes, nor what prerequisites apply.

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