mcp_opendaw_set_send_level

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

No annotations provided, so description must bear behavioral disclosure. It states the mutation action but does not mention side effects, error conditions, or required permissions. Minimal transparency.

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?

Three short sentences: one for purpose, then each parameter on its own line. Front-loaded and no redundant 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?

Given an output schema exists, return values need not be described. For a simple setter, the description covers core operation. Could add error handling notes but not essential.

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?

With 0% schema description coverage, the description adds semantic context by listing parameters with brief explanations (e.g., 'src_unit: Source audio unit index'). However, lacks details like valid ranges or constraints.

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 the send level for an existing aux send', specifying the verb (Set) and resource (send level). It distinguishes from sibling tools like create_send, list_sends, and set_send_pan.

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?

Implies use after send creation (references 'existing aux send' and 'send_index from create_send return'), but lacks explicit when/when-not guidance or alternative tool suggestions.

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