add_keyframe

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state what happens if a keyframe already exists at the given time, whether keyframes are inserted or overwritten, or what side effects occur in the timeline. The behavior is described only at the most basic action level.

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 clear sentence with no filler or redundancy. The core action and target are front-loaded, making it easy for an agent to parse quickly.

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 simple mutation tool with fully documented required parameters, the description is minimally adequate. However, the absence of annotations, output schema, and behavioral details such as duplicate-timestamp handling leaves notable gaps for an agent that needs to reason about edge cases.

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%, and each parameter already includes meaningful descriptions such as 'display name of the parameter' and 'The ID of the clip.' The tool description adds no additional semantic context beyond the schema, so the baseline of 3 is appropriate.

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 a specific verb ('adds'), a resource ('keyframe to a clip component parameter'), and a temporal qualifier ('at a specific time'). This distinguishes it well from sibling tools like remove_keyframe, get_keyframes, and set_keyframe_interpolation.

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?

The intended use is implied by the verb 'adds,' but there is no explicit guidance on when to choose this tool over related alternatives such as remove_keyframe or get_value_at_time. No exclusions or alternative mentions are provided.

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