mcp_opendaw_create_pitch_stretched_clip

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

Without annotations, the description carries full burden, but it only explains basic behavior (creates clip, uses specific play mode) and parameter meanings. It does not disclose side effects, prerequisites, error conditions, or overwrite behavior. The safety profile is not fully transparent.

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 concise with a summary line, a brief explanation, and a parameter list. Every sentence adds value, and the structure is clean and readable.

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 covers the basics but lacks details on return value, prerequisites (e.g., track must exist), and potential side effects. The output schema exists but is not shown, so completeness is adequate but not thorough.

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 compensates by explaining each parameter's meaning (e.g., sample_id from load_audio, clip_index as slot index). This adds significant value beyond the schema's simple 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 tool creates a pitch-stretched audio clip in session view, and distinguishes it from the sibling time-stretched version by emphasizing pitch alignment with tempo. The specific verb-resource combination and mention of AudioPitchStretchBox add clarity.

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 implies usage for maintaining pitch, but does not explicitly state when to use this tool versus the time-stretched alternative (mcp_opendaw_create_time_stretched_clip). No when-not-to-use or alternative guidance is provided.

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