remove_property_keyframe

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the destructive nature (removing keyframes) and an unusual post-condition — that it 'verify[s] that the keyframe count decreased'. However, it omits whether removal is reversible/undoable, what happens when no keyframe exists at the target time, and how tolerance_seconds affects matching.

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?

A single front-loaded sentence with no filler; the mode clarification is parenthetical and efficient. It could be tighter still, but nothing is wasted.

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 13-parameter, destructive, annotation-free tool with no output schema, the description is adequate but thin. It never explains how the clip/track/component/property selectors combine, how tolerance works, or the failure mode when the keyframe count does not decrease.

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 85%, so the schema already documents nearly all 13 parameters. The description reinforces the single-time vs range behavior but adds no syntax or format detail beyond the schema, and says nothing about tolerance_seconds or the clip/track targeting params.

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 gives a specific verb and resource ('Remove a keyframe ... from a clip component property') and clarifies the two operating modes (single time point or a time range). It is readily distinguishable from siblings like add_property_keyframe, update_property_keyframe, and get_property_keyframes, though it never names them explicitly.

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?

It states what can be removed but never says when to choose this tool over update_property_keyframe (e.g., setting a value to null) or how removal interacts with surrounding keyframes. No prerequisites, no exclusions, no alternatives are offered.

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