ae_set_audio_levels

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

With no annotations, the description carries full burden. It usefully discloses that the operation is grouped into 'One undo step', but omits prerequisites (does the layer need to be an audio layer? is an active comp required?) and what happens to existing levels/keyframes when overwriting.

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?

Two tight sentences with the primary action front-loaded and the undo note trailing efficiently. Nothing is wasted, though it is sparse rather than rich.

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 7-parameter mutation tool with no annotations and no output schema, the description covers purpose, modes, and undo behavior but leaves open layer-type requirements, active-comp dependency, and stereo left/right handling. Adequate but with clear gaps.

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 coverage is 71% (mid-range), so the schema documents most fields. The description still adds real interpretation beyond the schema by framing the mutually distinct modes: a bare level (static), level+time, or a keys array, plus the dB unit semantics.

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?

States a specific verb+resource ('Set Audio Levels (dB) of a layer') and enumerates the three operating modes (static, at a time, keyframes). It distinguishes itself from generic setters like ae_set_property by scoping to audio levels, though it never names a sibling alternative.

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 mention of 'static, at a time, or as a list of keyframes' implies the three invocation patterns an agent can pick, which is genuine usage context. However, there is no explicit when-to-use/when-not guidance or routing against ae_set_property or ae_set_keyframes.

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