set-audio-levels

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

The description indicates the tool sets audio levels and supports keyframing, but lacks details on behavior like overriding existing keyframes, interaction with current levels, or effects on the timeline. While annotations are absent, the description partially covers behavioral traits.

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 sentence that is front-loaded with the primary action and includes essential details without waste. Every word contributes 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?

Given no output schema, the description covers the main functionality, but omits information on return values, error conditions, or the effect of multiple calls. It is adequate but could provide more context for complex usage.

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 schema provides 100% coverage of parameters, and the description adds value by summarizing features (per-channel control, optional keyframing) that map to leftLevel, rightLevel, and timeInSeconds, going beyond individual parameter descriptions.

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 audio levels), the resource (audio or AV layer), and key features (per-channel control, optional keyframing). It differentiates from sibling tools like 'analyze-audio-waveform' and 'get-audio-info' by specifying a mutation action.

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 clear context for when to use the tool (setting audio levels for layers), but does not explicitly state when not to use it or mention alternatives. Usage is implied by the action, but no exclusions or comparisons are given.

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