copy_keyframes

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

No annotations exist, and the description only says 'copy', giving no behavioral details. It does not disclose whether target property gets overwritten or appended, whether source must have keyframes, or any side effects. The description carries the full burden and fails.

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, which could be concise if it packed information, but it lacks essential details. For a tool with 9 parameters and no schema descriptions, this is under-specification, not conciseness.

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?

No output schema, no annotations, and a single sentence cannot adequately describe a complex operation with 9 parameters. Given the sibling tools for keyframe manipulation, this description fails to provide enough context for correct usage.

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 0% and the description adds zero meaning to any of the 9 parameters. Terms like sourceProperty, targetProperty, compId, layer identifiers are left undefined. The description does not help the agent understand parameter roles.

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 action 'copy keyframes' from one property to another. However, the term 'property' is ambiguous and does not differentiate from sibling tools like set_keyframe or get_keyframes, which also operate on properties. The verb+resource is specific, but lacks scope details.

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 vs. alternatives (e.g., offset_keyframes, duplicate keyframes manually). No prerequisites, when-not-to-use, or context are mentioned.

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