raw_track_gain

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does acknowledge potential side effects ('May open a dialog or change project state'), but it does not explain what state changes may occur, whether a focused track is required, or what happens if none is focused. The instruction to 'inspect the command name first' is vague and shifts responsibility to the agent.

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 short and front-loaded with the primary purpose. The second and third sentences add some behavioral caution, though 'Static no-argument Audacity action' is partially redundant with the empty schema.

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 no-argument tool, the description covers the main action and flags potential side effects, which is adequate. However, it does not clarify what 'focused track' means, what the dialog does, or whether the tool is safe to invoke without user confirmation. The hedging phrase 'inspect the command name first' suggests the definition itself is incomplete.

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 has 100% coverage by virtue of being empty. The description reinforces this with 'no-argument,' which is sufficient since there is no parameter meaning to clarify.

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: 'Open the gain dialog for the focused track.' This is a specific verb and resource, and it is implicitly distinguished from sibling tools like raw_track_gain_dec and raw_track_gain_inc. However, the added caveat 'May open a dialog or change project state' introduces some uncertainty about the exact behavior.

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 guidance on when to use this tool versus alternatives such as raw_track_gain_dec, raw_track_gain_inc, or raw_track_pan. 'Inspect the command name first' is more of a caution than a usage guideline, and no when/when-not conditions are provided.

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