mcp_opendaw_set_waveshaper_equation

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

No annotations are provided, so the description must convey behavioral traits. It explains that this sets a transfer function (a mutation) and enumerates equation options with brief descriptions. However, it does not disclose side effects (e.g., whether it replaces the current equation), error conditions (e.g., invalid effect_index), or permission requirements. More transparency is needed.

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 well-structured: a brief first line summarizing purpose, followed by parameter listings and equation details. It is reasonably concise, with each sentence adding value. Minor redundancy (e.g., repeating equation in list) could be trimmed, but overall effective.

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?

Given that an output schema exists, return values are not needed. The description covers the core functionality and parameters but lacks prerequisites (e.g., need a Waveshaper effect added first) and error handling. For a mutation tool among many siblings, additional contextual guidance would improve completeness.

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%, so the description must compensate. It provides meaningful explanations for all three parameters: unit_index (AU index), effect_index (must be a Waveshaper), and equation (lists all valid values with descriptions). This adds significant value beyond the raw schema, though it could elaborate on constraints like valid ranges.

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 'Set the transfer function equation on a Waveshaper effect' with a specific verb and resource. It distinguishes itself from sibling 'set_' tools by explicitly targeting a Waveshaper effect, which is unique among the many set tools listed.

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 effect_index to be a Waveshaper but does not explicitly state when to use this tool versus alternatives. It lacks exclusion criteria or context about prerequisite steps (e.g., adding a Waveshaper first). The equation options are listed but without guidance on selecting based on desired sonic outcome.

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