mcp_opendaw_augment_notes

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

No annotations are provided, so the description carries the full burden. It explains the effect on durations, mode behavior (scale vs stretch), and return values (counts of augmented and skipped notes). It does not explicitly state that the tool mutates project state, but the mutation is implied. Could be improved with a caution about destructive changes.

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 thorough but verbose, including historical examples and references that may not be essential for an LLM agent. While the first sentence front-loads the purpose, the subsequent paragraphs add context that could be trimmed. Adequate, but could be more concise.

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 no annotations and an empty schema, the description covers all necessary information: tool intent, parameter explanations, mode behavior, and return format. It accounts for the tool's complexity and provides enough context for an agent to use it correctly. The output schema exists but is not needed for completeness.

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 coverage is 0%, so the description must compensate fully. It explains factor range (0.25-4.0), default for region_index (-1 = all regions), and mode options with detailed examples of 'scale' (multiply duration and position) vs 'stretch' (duration only). All five parameters are meaningfully described, adding value beyond the bare schema.

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 tool augments or diminishes note durations, positions it as the fourth classical transformation, and differentiates it from siblings like transpose, reverse, invert. Musical examples (Beethoven 5th, Bach fugues) reinforce the purpose and distinguish it from other 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 explains when to use the tool (for duration changes with factor >1 or <1) and provides mode options. However, it does not explicitly mention when NOT to use it or compare with sibling tools like scale_durations, which also modifies durations. Lacks explicit alternative guidance.

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