create_clip

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

The description discloses the default length parameter (4.0 beats) but does not mention side effects like overwriting existing clips or error conditions. With no annotations provided, the description carries the burden but only partially fulfills it.

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 at 4 lines plus parameter list, front-loading the purpose. Every sentence is informative, though it could be more tightly structured.

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?

No output schema or annotations exist, and the description does not explain the return value, side effects, or errors. For a creation tool, this lack of context impairs an agent's ability to use it correctly.

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 parameter explanations in the description (track_index, clip_index, length) add significant value beyond the bare schema. The descriptions are clear and include a default value.

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 new MIDI clip in a specified track and clip slot, using specific verbs and resource. However, it does not explicitly differentiate from sibling tools like add_notes_to_clip, which is acceptable.

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 is provided on when to use this tool versus alternatives such as fire_clip or stop_clip. The description lacks context about prerequisites or appropriate usage scenarios.

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