mcp_opendaw_find_overlapping_notes

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

With no annotations, the description carries the full burden. It discloses the return format (list of overlapping notes or error) and scopes the operation to a note region, but does not explicitly state that it is read-only or describe any side effects. This is adequate but not rich; a read-only hint would have been helpful.

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 compact and well-organized: a one-sentence purpose, a use-case note, then a flat parameter definition list, and a return statement. Every sentence adds value; there is no filler or 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 fully explains the tool's inputs, purpose, and output, and the presence of an output schema covers return structure. It lacks explicit edge-case handling (e.g., empty results, invalid beat ranges), but overall it is complete enough for the tool's complexity.

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 description coverage is 0%, so the description must compensate. It defines all six parameters thoroughly, including types (MIDI note, beats) and examples (60 = C4), giving the agent complete understanding beyond the bare schema. This is exemplary compensation.

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 uses a specific verb (Find) and clearly defines the resource: notes overlapping a pitch and time range within a note region. It distinguishes itself from sibling tools by focusing on collision detection and chord/harmony finding, which is unique among the many note tools.

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 explicitly states two use cases: checking if a note can be placed without collision and finding chords/harmonies at a pitch range. It does not mention when not to use it or name alternatives, but the provided context is clear enough for an agent to decide when to invoke it.

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