Keyframe a clip (Motion/Opacity)

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

Disclosures 'VERIFIED scriptable' and notes speed ramps are not reliably scriptable. Annotation already marks destructiveHint=true, but description adds meaningful context about reliability and limitations.

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?

Two sentences, front-loaded with purpose. Second sentence packs many details but remains readable. Could be slightly more structured, but efficient overall.

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?

Covers all four parameters, required fields, key structure, interpolation options, and usage example. No output schema, but description compensates with complete parameter guidance.

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?

100% schema coverage so baseline 3. Description adds value by explaining each property, the key value format, interpolation types, and giving a concrete example (push-in with scale).

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?

Clearly states 'Animate a clip with keyframes' and lists the exact properties (scale, opacity, rotation, position). Distinguishes from siblings by focusing on keyframing versus adding effects or transitions.

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?

Explicitly warns against using for speed ramps (not reliable) and directs to 'bake into the Remotion render' as alternative. Provides both when-to-use and when-not-to-use guidance.

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