adjust_audio_levels

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, but it only restates that volume is adjusted. It does not reveal whether the change is absolute or relative, whether it is undoable, or whether existing keyframes or gain automation are affected, which is significant for a mutating operation.

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, front-loaded sentence with no filler or redundancy. It is immediately scannable and every word contributes to the core meaning.

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 two-parameter setter, the description plus schema provides enough to construct a correct call. However, without annotations, an output schema, or any usage/behavioral guidance, it is only minimally complete and leaves the sibling-selection problem unresolved.

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 input schema already documents both parameters completely, including that level is in decibels and can be positive or negative, so schema coverage is 100%. The description adds no parameter-level detail beyond the schema, but since the schema fully covers semantics, baseline 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 action ('Adjusts') on a specific resource ('volume (gain) of an audio clip on the timeline'), so an agent can understand the core purpose. It does not, however, differentiate it from the closely-named sibling tool set_clip_volume, which likely targets the same property, so it does not earn a 5.

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 gives no guidance on when to use this tool instead of set_clip_volume, mute_track, setup_ducking, or add_audio_keyframes. There are no explicit use cases, prerequisites, or exclusions, leaving the agent to choose among several volume-related sibling tools without additional context.

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