Add an audio volume keyframe to a clip at a specific time to control volume changes during playback.
Add an audio volume keyframe to a clip at a specific time
| Name | Required | Description | Default |
|---|---|---|---|
| time | Yes | Time in seconds relative to clip start | |
| volumeDb | Yes | Volume in decibels at this keyframe | |
| clipIndex | Yes | Clip index | |
| trackIndex | Yes | Audio track index |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It says only that a keyframe is added, without explaining duplicate-keyframe behavior, required permissions, whether changes are undoable, or what the response contains.
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?
It is a single front-loaded sentence with no filler. The action, target, and key input concept are all expressed efficiently.
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 four-parameter mutation tool with fully documented schema fields, the description is adequate to identify the operation. However, with no annotations or output schema, it should say more about mutation behavior and alternatives.
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%, so all four parameters are already documented in the schema. The description reinforces that the operation targets audio volume at a specific time but adds no format, range, or edge-case semantics beyond that.
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 a specific verb and resource: adding an audio volume keyframe to a clip at a given time. It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools such as add_keyframe or set_clip_volume.
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 description provides no guidance on when to use this tool instead of alternatives like add_keyframe or set_clip_volume. It implies usage from the name and purpose but includes no exclusions or routing advice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.