raw_set_track_audio

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

With no annotations, the description carries the full burden of disclosing behavior. It usefully warns that the action 'may open a dialog or change project state,' which signals side effects and potential blocking. However, it is vague about what state changes occur, whether a track must be selected, and whether the operation 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?

Two short sentences convey purpose, invocation style, and the key caveat about dialogs and project state. The warning is front-loaded enough for an agent to notice before invoking the tool, and there is no wasted text.

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?

The description covers the essential caveat that this may open a dialog or change project state, which is critical for a raw action. It does not, however, mention which track is affected, whether selection is required, or what the tool returns, leaving some ambiguity despite the zero-parameter simplicity.

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 tool has zero parameters and the schema already shows an empty properties object, so there is little semantic burden. The description reinforces this with 'no-argument,' and no parameter documentation is needed beyond that.

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 identifies a specific verb and resource: 'Set audio properties (mute, solo, gain, pan) for a track.' This makes the core purpose clear and loosely differentiates it from single-property siblings like raw_track_mute and raw_track_pan, though it does not explicitly name those alternatives.

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?

There is no explicit guidance about when to use this tool versus the many raw_track_* siblings. 'Static no-argument Audacity action' gives context, but the description does not say when this is preferable or when a more specialized tool should be used instead.

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