remove_keyframe_range

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

With no annotations, the description carries the full burden of behavioral disclosure. It only restates the action without explaining what constitutes a 'range,' whether it affects all properties or just the selected one, or any side effects such as deletion confirmation or undo behavior.

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 short and to the point, but the phrase 'Premiere Pro expanded operation' is filler that does not add substance. It could be simplified to just 'Remove keyframe range.'

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 existence of sibling tools like 'remove_keyframe' and 'get_keyframes,' the description should clarify how a range is specified and whether this is a destructive or reversible operation. The current description leaves too much unspecified for a tool that mutates keyframe data.

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?

There are zero parameters, so the description is not expected to explain parameter meanings. The baseline of 4 applies, and the description does not introduce any parameter-related confusion.

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 states 'remove keyframe range,' which clearly indicates the action of removing keyframes over a range. The word 'range' distinguishes it from the sibling tool 'remove_keyframe,' though the phrase 'expanded operation' adds no clarity.

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 instead of 'remove_keyframe' or how the range is defined. The description does not mention prerequisites such as selecting a clip or setting a playhead range.

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