mcp_opendaw_create_chop

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 describes the operation, parameter effects, and return values ('Returns notes created, segment count, mode used'), but does not disclose potential side effects like overwriting existing notes or prerequisites beyond implied track/unit indices.

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 long but every sentence earns its place: a crisp purpose statement, musical context, per-parameter explanations, and return summary. The use of line breaks per parameter improves scannability 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?

Given 12 parameters, no annotations, and an output schema (existence noted), the description covers all parameter semantics, usage context, and return information. Missing only explicit side-effect warnings, but for a 'create' operation this is a minor gap, not a critical deficiency.

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%, but the description compensates fully by explaining every parameter with defaults, ranges, and examples (e.g., stutter_count 2-8, octave_shift -1 for bass chops, velocity_variation 0-0.5). This is far beyond what the schema provides.

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 opens with a specific verb and resource: 'Create a chop — slice source pitches into segments and rearrange them.' It clearly differentiates from sibling tools like create_stutter by presenting chop as the umbrella technique with multiple rearrangement modes, including stutter as one of them.

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?

Provides strong musical context ('quintessential hip-hop/EDM sampling technique', Dilla chops, glitch-hop) that implies when to use this tool. However, it does not explicitly name alternative tools (e.g., create_stutter) or specify when not to use it, leaving some room for interpretation.

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