create_clip

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

With no annotations provided, the description carries the full burden of disclosing side effects. It does not state whether an existing clip in the slot will be overwritten, what happens if the track or slot is invalid, or what the return value is. The only behavioral hint is 'create a new MIDI clip,' which is minimal.

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 and front-loaded with the main purpose sentence, followed by a clear parameter list. Each line earns its place by adding meaning beyond the schema. It is not overly verbose, though it could omit the parameter list if the schema already had descriptions.

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?

For a mutation tool with no annotations and no output schema, this description is incomplete. It fails to disclose key behaviors such as overwrite semantics, required preconditions, or error handling. The agent cannot fully anticipate the tool's effects or outcomes.

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 is the sole source of parameter meaning. It explains all four parameters, including the default for length ('4.0 beats') and the telemetry purpose of user_prompt. This adds value beyond the names, though track_index and clip_index are relatively self-explanatory.

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 states precisely 'Create a new MIDI clip in the specified track and clip slot,' which conveys the exact action and target resource. It clearly distinguishes this from sibling tools like create_audio_clip and create_midi_track by specifying 'MIDI' and 'clip slot.'

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—when you need to create a new empty MIDI clip—but it does not explicitly state when to prefer this over alternatives like add_notes_to_clip or generate_chord_progression. No exclusions or alternative tools are mentioned, so guidance is only implied.

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