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

Annotations only declare readOnlyHint=false, so the mutation nature is known. The phrase 'the renderer honors it' usefully implies this stores an intent rather than immediately rewriting audio, but the description doesn't say whether the setting persists across renders, affects only the project, or is reversible.

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?

A single compact sentence with the core action front-loaded and the parenthetical qualifiers placed after. No wasted words, though the 'by role' clause is ambiguous enough to cost a point.

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?

This is a mutation tool with no output schema and only partial behavioral detail. An agent cannot tell whether the change applies immediately, requires a re-render, or how it relates to the sibling audio tools, leaving real gaps for a write operation.

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 67% and duck_level ('Music level under voice, 0-1 (default 0.3)') and project_id are already documented in the schema, so baseline is 3. The description adds nothing about how 'enabled' interacts with duck_level (e.g., whether the level is ignored when disabled) or what 'by role' means absent a role parameter.

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?

Specific verb (configure) plus resource (voice-over-music ducking mix) with scope caveat 'by role' and the note that the renderer honors it. It is distinguishable from the many studio.* siblings, though it doesn't name the closest audio-levels 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?

No guidance on when to choose this over studio.adjust_audio_levels, studio.set_track_muted, or studio.enhance_audio, and no prerequisites such as needing voice and music tracks present. Usage is only inferable from the noun phrase 'ducking mix intent'.

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