set_bus_fader

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

No annotations are present, so the description must fully disclose behavioral traits. It only states the basic action and bus parameter format, omitting details like level range, side effects, or whether the change is immediate and 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 concise sentences convey the core information without redundancy. The first sentence states the action and unit, the second clarifies the bus parameter. No filler or irrelevant details.

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?

With an output schema present, the description need not explain return values. However, for a simple setter tool, missing details like valid level range or constraints on 'level_db' reduce completeness. The description covers the essential purpose but leaves gaps.

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 0%. The description partially compensates by clarifying that 'bus' can be a number (1-6) or name. However, 'level_db' receives no additional semantics beyond being a number in dB, which is already implied.

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'), resource ('bus master fader'), and unit ('dB'). It implicitly distinguishes from sibling tools like set_channel_fader and set_main_fader by specifying 'bus', making its purpose unambiguous.

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 use this tool versus alternatives (e.g., set_channel_fader, set_main_fader). No prerequisites, context, or exclusions are provided, leaving the agent without strategic usage context.

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