scale_keyframe_timing

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

With no annotations provided, the description must fully disclose behavior. It states the operation speeds up or slows down keyframe timing, but does not mention whether it is destructive, what happens to keyframe values, how anchorTime affects the operation, or any requirements like property type or keyframe selection.

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 a single sentence and front-loaded with the action, making it concise. However, it is too minimal for the tool's complexity, omitting essential details, so it is not as effective as it could be.

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?

Given 7 parameters, no annotations, and no output schema, this one-sentence description is inadequate. It does not explain how the scale factor is interpreted, what anchorTime does, or how the target layer or composition is specified, creating significant gaps for an agent to correctly use the tool.

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 only 29%, with only 'scale' and 'anchorTime' having descriptions. The tool description adds no parameter meaning beyond the schema; critical parameters like property, compId, compName, layerName, and layerIndex remain unexplained, leaving the agent without enough information to invoke the tool correctly.

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 uses the specific verb 'Scale' and resource 'keyframe timing', with a parenthetical clarifying the effect as 'speed up or slow down'. This makes the tool's purpose clear and distinguishes it from related operations like offset or reverse, though it doesn't explicitly name alternative tools.

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 is given on when to use this tool versus alternatives such as offset_keyframes or reverse_keyframes. The parenthetical implies timing adjustments, but there are no explicit use cases, exclusions, or recommendations for other timing edits.

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