mcp_opendaw_create_note

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

With no annotations provided, the description carries the full burden. It discloses the auto-creation of clips and that notes are added to the first clip. However, it does not mention error conditions, what happens with multiple clips, or return value.

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?

The description is concise and well-structured: purpose first, then parameter list with bullet-like clarity, followed by behavioral notes. Every sentence provides value without redundancy.

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?

The description lacks information about the return value or output schema, which is listed as existing but not described. For a creation tool, this is a notable gap. Additionally, it does not cover edge cases like invalid parameter values.

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?

Despite 0% schema coverage, the description explains each parameter with examples (e.g., pitch: 60 = C4) and ranges (velocity: 0.0-1.0). It adds significant meaning beyond the schema's type and name.

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 starts with 'Create a MIDI note on a note track,' clearly stating the action and resource. This differentiates it from sibling tools like 'create_notes_batch' (batch creation) and 'create_note_clip' (clip creation).

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?

The description provides parameter details and mentions automatic clip creation, but it does not explicitly state when to use this tool versus alternatives or when not to use it. The context is implied but lacks explicit guidance.

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