mcp_opendaw_set_note_advanced

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 skip values for leaving properties unchanged and notes that the tool 'Returns updated values, or error.' This provides good transparency about behavior, though it does not detail potential side effects or permissions needed.

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 well-structured: a concise summary line, bullet lists for properties and indices, a clear skip instruction, and a return statement. Every sentence adds value, and it is front-loaded with the most important 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 the tool's complexity (8 parameters, 0% schema coverage, no annotations), the description covers all necessary context: parameter meanings, ranges, skip behavior, and return value. It is complete enough for an agent to use 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?

Schema description coverage is 0%, so the description fully compensates by explaining all 8 parameters: the four advanced properties with ranges and defaults, the four index parameters, and the skip mechanism. This adds significant meaning beyond the minimal 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 'Set advanced note properties' and lists specific properties (chance, cent, playCount, playCurve), distinguishing it from basic set_note_properties and other sibling tools. The title and first line make the purpose 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?

The description explains that these properties are beyond basic ones and provides instructions on skipping properties with -1 or -999. However, it does not explicitly contrast with sibling tools like set_note_cents or set_note_properties, which could guide the agent's choice more directly.

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