mcp_opendaw_replace_instrument

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

Discloses that it deletes old instrument and creates new one, returns old/new types. Specifies preconditions (CaptureMidiBox) and limitations (not for tape). Lacks details on side effects like preservation of effects or automation, but given no annotations, this is thorough.

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?

Description is compact with no redundant sentences. Starts with action, then API, then constraints, then parameters. Could benefit from bullet points for parameters, but overall well-structured.

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 purpose, constraints, parameters, return value, and distinguishes from dozens of siblings. Despite no annotations, provides all information needed for an agent to decide and invoke correctly.

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?

Compensates for 0% schema coverage by explaining unit_index must be >=1 and listing exact factory keys for new_instrument. Provides valid values and constraints, enabling correct tool invocation.

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 it replaces the instrument on an audio unit with a different MIDI instrument. Specifies the API used and constraints on instrument types (only MIDI, not tape), distinguishing it from create/manage instrument siblings.

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?

Provides clear context on when to use (replace MIDI instrument) and constraints (only for specific instruments, AU must have CaptureMidiBox). Does not explicitly contrast with alternatives like replace_from_preset, but constraints effectively guide usage.

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