mcp_opendaw_set_effect_parameter

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

No annotations provided. Description covers the write operation but does not mention error conditions, return value, or prerequisites (e.g., effect existence). With no annotations, more transparency is expected.

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?

Well-structured with a clear opening, parameter list, and examples. Could be slightly more concise but examples are helpful.

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?

Covers input well but does not mention output or error handling. Output schema exists but not described. Lacks discussion of side effects or prerequisites.

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%, but description explains each parameter meaningfully, including examples and special cases for string values. Adds significant value beyond the schema.

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?

Description clearly states 'Set a parameter on an audio effect' and specifies indices and parameter names. Examples differentiate from typed siblings like set_effect_parameter_bool.

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?

Explains parameters, references list_effect_parameters for names, and provides examples. Includes special case for string params via parameter_name='equation'. Could be more explicit about when to use this vs typed variants.

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