live_create_clip

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

No annotations are provided, so the description must disclose behavioral traits. It mentions default length but omits key behaviors like whether an existing clip is overwritten, the role of the confirm parameter, or that it operates on the session grid. Minimal disclosure beyond the schema defaults.

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?

Two short sentences, each adding value. The first defines the core purpose, the second provides a useful default. No extraneous words.

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 5 parameters, an output schema, and siblings that target different views, the description is too sparse. It fails to specify that the tool creates in the session slot (vs arrangement), does not explain confirmation behavior, and does not clarify the indexing for track and scene. The output schema exists but the description provides no 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 description coverage is 0%, so the description must add meaning. It only mentions length_beats defaults. It does not explain track_index, scene_index, name, or confirm parameters. The agent must infer their roles from the tool name and context.

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 a specific verb ('Create') and resource ('empty MIDI clip in the given session slot'). It clearly distinguishes from sibling tools like live_arrangement_create_midi_clip (arrangement view) and live_delete_clip.

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?

No guidance on when to use this tool over alternatives, such as live_arrangement_create_midi_clip for arrangement view or live_set_clip_notes for populating the clip. No exclusions or context provided.

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