mcp_opendaw_set_vocoder_band_count

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

With no annotations, the description carries the burden. It discloses that effect_index must point to a Vocoder effect but does not mention immediate effects, reversibility, or return values. Partial transparency.

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: two sentences plus a list of three parameters. It is front-loaded with the purpose and contains no unnecessary information. Every sentence adds value.

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 simple setter, it covers purpose, parameters, and typical values. It does not discuss error conditions or validation, but output schema exists so return values are handled. Minor gap: band_count values are not enforced by schema.

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 0%, so description compensates well. It explains each parameter: unit_index as AU index, effect_index as effect index (must be Vocoder), and band_count with typical values (8,16,24,32). This adds meaning beyond the integer type.

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 the band count on a Vocoder effect' and specifies the resource (Vocoder effect) and attribute (band count). It gives a typical range (8-32) and distinguishes from siblings like set_vocoder_modulator_source, which sets a different parameter.

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?

The description implies usage by requiring a Vocoder effect but does not explicitly state when to use this tool versus alternatives. It lacks guidance on conditions or when not to use it.

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