mcp_opendaw_set_send_routing

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

No annotations provided. The description minimally discloses behavior: sets routing mode with two possible values and a default. Does not mention side effects, permissions, or safety implications of changing routing.

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?

One sentence plus a concise parameter list. Purpose is front-loaded. No redundant or irrelevant information.

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?

Adequately covers the tool's operation and parameter meanings for a simple setter. Output schema exists, so return values are not needed in description. Could mention error conditions or prerequisites but not critical.

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 the description explains each parameter: unit_index as source audio unit, send_index as index on source AU, and routing as 'pre' or 'post' with default. This adds meaning beyond the schema's titles.

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 verb 'Set' and the resource 'routing mode for an aux send', specifying pre-fader or post-fader. It distinguishes from sibling tools like set_send_level and set_send_pan by focusing on routing mode.

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, or prerequisites (e.g., send must exist). The description lacks context about when pre vs post routing is appropriate.

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