mcp_opendaw_list_notes

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

The readOnlyHint annotation already marks this as safe, and the description does not contradict that. Beyond the annotation, it adds valuable behavioral context: unit_index -1 searches all audio units, and results are sorted by position. It also discloses the exact return fields, which helps set expectations. This adds genuine value beyond the annotation.

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-structured: a one-line purpose, a brief return format section, and a parameter list. Every sentence adds necessary information, with no fluff. The line breaks separate logical components, making it easy to scan. This is a model of concise technical writing.

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?

For a simple read-only list tool, the description fully covers the purpose, all parameters, return value semantics (position, duration, pitch, velocity, cent, chance), and sorting behavior. An output schema exists, so the return format is further specified, but the description already provides the key fields. No significant gaps remain for an agent to invoke the tool 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?

The schema has 0% description coverage, so the description carries the burden. It explains all three parameters: unit_index (-1 = search all AUs), track_index (note track within the AU), and region_index (0-based region). However, track_index is slightly ambiguous regarding whether it is 0-based or scoped within the AU; the -1 wildcard behavior is only explained for unit_index, not track_index. Still, the description provides substantive meaning beyond the bare schema 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 action: 'List all note events within a region.' It specifies the resource (note events within a region) and distinguishes itself from siblings like list_note_regions and list_automation_events. The verb 'list' is specific and unambiguous.

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?

Usage is implied: the description indicates this tool lists note events within a region, so an agent can infer when to use it. However, it does not explicitly name alternatives (e.g., list_note_regions for regions) or provide when-not-to-use guidance. The context clues from siblings help, but the description itself offers no exclusions or alternative recommendations.

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