copy_keyframes

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

With no annotations, the description alone must explain side effects. It states 'copy' but does not clarify whether the source is modified, whether existing target keyframes are overwritten, or if the operation is reversible. This lack of detail obscures the tool's behavioral impact.

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, concise sentence with no redundancy. It is efficient, though its brevity contributes to the lack of substantive information. Still, for the content it does convey, it is well-structured and free of fluff.

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 the tool's complexity (nine parameters, no output schema, and many sibling operations), the description is severely incomplete. It does not explain how parameters interact, what the expected result looks like, or any error handling. The tool appears to require more documentation to be usable by an agent.

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?

The schema provides nine parameters with no descriptions, and the tool description offers no explanation of any parameter. For instance, 'sourceProperty' and 'targetProperty' are self-explanatory, but 'compId', 'timeOffset', and the layer identifiers lack context. The description adds zero semantic value to the parameter list.

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 tool's function (copy keyframes from one property to another) using a specific verb and resource. It distinguishes from sibling tools like set_keyframe or offset_keyframes by focusing on copying, though it lacks detail on what 'property' and 'keyframes' entail in this context.

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 provided on when to use this tool versus alternatives. Given the large number of sibling tools for keyframe operations (e.g., offset, scale, reverse), the model receives no indication of when copying is the appropriate operation, leaving usage ambiguous.

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