set-audio-levels

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

No annotations are provided, so the description carries the full burden. It mentions per-channel control and optional keyframing but does not disclose what happens if no level is provided, whether existing levels/keyframes are overwritten, or any side effects. The behavior is only superficially summarized, adding little beyond the schema.

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, well-structured sentence that starts with the action and resource, then adds key features. No wasted words, and it conveys the essential purpose effectively.

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?

Despite the schema documenting parameters, the overall tool behavior is under-specified. It does not clarify required parameters' roles, the effect of omitting optional level fields, or how keyframing behaves (e.g., whether it replaces existing keyframes). With no annotations and no output schema, more context is needed for an agent to use it correctly.

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 the baseline is 3. The description only paraphrases what the schema already states (per-channel via leftLevel/rightLevel, keyframing via timeInSeconds) without adding new contextual meaning or usage details.

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 the action ('Set'), the resource ('audio levels'), and the unit ('dB'), and specifies the target ('audio or AV layer'). It also mentions per-channel control and keyframing, which distinguishes it from sibling tools like setLayerKeyframe that handle generic layer properties.

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 implies usage: when you need to adjust audio levels on a layer. However, it does not explicitly suggest when to prefer this over alternatives like setLayerKeyframe or animate-to-audio, nor does it mention any exclusions or prerequisites.

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