remove_keyframe_range

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

No annotations are present, so the description is the sole source of behavioral information. It merely repeats the tool name without disclosing side effects, destructiveness, or what 'range' refers to. The phrase 'Premiere Pro expanded operation' adds no behavioral insight.

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 but wastes space on 'Premiere Pro expanded operation', which adds no substantive value. The rest essentially restates the tool name. This is under-specification rather than efficient 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?

With no annotations, no output schema, and no parameter details, the description must explain what a keyframe range is, how it is determined, and what prerequisites exist. It only states the basic action, leaving the tool's operation incomplete for 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 tool has zero parameters, and the description need not explain any. With 0 parameters, the baseline is 4, and the schema already reflects the parameter count, so the description adding no parameter detail is acceptable.

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 the action 'remove keyframe range' clearly and distinguishes from the sibling tool 'remove_keyframe' by specifying 'range'. However, the phrase 'expanded operation' is vague and does not clarify what 'expanded' entails, slightly reducing 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 versus the sibling 'remove_keyframe' or any other alternative. The description lacks context about prerequisites, selection requirements, or conditions under which this tool should be preferred.

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