osc_set_bus_fader

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

No annotations are provided, so the description carries full burden. It states 'Set' implying a write/mutation operation, but doesn't disclose any behavioral traits like whether this requires specific permissions, if changes are immediate or reversible, potential side effects, or how it interacts with other mixer controls. For a mutation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after setting the fader, what the expected response might be, error conditions, or how this operation fits within the broader mixer control context. Given the complexity of audio mixing and many sibling tools, more context would be helpful.

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 description coverage is 100%, so the schema already fully documents both parameters (bus number 1-16 and fader level 0.0-1.0). The description doesn't add any additional meaning or context about these parameters beyond what the schema provides, so the baseline score of 3 is appropriate.

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') and target resource ('fader level for a mix bus'), making the purpose immediately understandable. It distinguishes from siblings like osc_set_aux_fader by specifying 'bus' rather than 'aux', but doesn't explicitly contrast with osc_set_fader which might handle channels instead of buses.

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 is provided about when to use this tool versus alternatives. With many sibling tools like osc_set_aux_fader, osc_set_fader, and osc_set_main_fader, the description doesn't indicate whether this is for mix buses specifically or how it differs from other fader-setting tools.

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