mcp_opendaw_remove_effect

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

No annotations are provided, so the description carries full burden. It only states 'Remove an audio effect' without disclosing behavioral traits like destructive nature, undoability, or chain shuffling. The parameter descriptions add no behavioral context.

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?

Extremely concise: two sentences plus two parameter lines. Front-loaded with the main purpose. No unnecessary words.

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?

While the description tells what and how to remove, it lacks context about the effect chain behavior (e.g., effects shift), how to obtain indices (e.g., using list_effects), and differentiation from similar remove tools. The existing output schema may supplement return details, but the description is incomplete for a DAW removal operation.

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% (no parameter descriptions), but the description adds meaning by specifying that unit_index is 'Audio unit index' and effect_index is 'Effect position to remove (0-based)'. This clarifies indexing and scope beyond the basic 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 'Remove' and the resource 'audio effect from an audio unit's chain', which distinguishes it from sibling tools like remove_midi_effect (MIDI effects) and remove_audio_bus (buses). The verb and resource are specific.

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 such as remove_midi_effect or remove_audio_bus. No prerequisites or context provided beyond parameter explanations.

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