create_clip

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

Describes failure conditions and length units beyond annotations (destructiveHint: false). Discloses that clip creation fails if slot occupied or track is audio, adding context. No contradiction with annotations.

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?

Three sentences: purpose, preconditions/length explanation, and typical usage chain. All sentences are essential, no waste, front-loaded with key 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?

Covers purpose, key parameters, failure modes, and usage flow. Output schema exists so return value explanation is unnecessary. Could mention defaults for empty clip (e.g., no notes), but generally complete for this tool.

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?

Input schema has 0% coverage, but description explains length parameter in beats (4.0 = one 4/4 bar). It indirectly clarifies clip_index and track_index by referencing 'Session slot' and failure when slot has a clip. Adds significant value for a low-coverage 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?

Description clearly states 'Create an empty MIDI clip in a Session slot', using a specific verb and resource. It distinguishes from sibling tools like create_audio_clip and add_notes_to_clip by specifying MIDI and slot context.

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?

Explicitly states failure conditions (slot occupied, audio track) and suggests alternatives (pick another clip_index or delete_clip). Provides a typical usage chain: create_clip -> add_notes_to_clip -> fire_clip/duplicate_to_arrangement, guiding when to use this tool.

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