commit_groove

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

In the absence of annotations, the description discloses the key behavioral trait of permanence ('make it permanent'), which signals an irreversible mutation of the clip. However, it does not mention other side effects, such as whether the original groove remains, whether undo is possible, or if the operation only affects session clip notes.

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 a clear purpose statement before the parameter list. The parameter descriptions are minimal but not verbose, and the overall length is appropriate for the tool's apparent simplicity, though it could benefit from a more structured format.

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?

With no annotations, no output schema, and only two parameters, the description is thin. It does not explain preconditions (e.g., a groove must exist in the groove pool), the distinction from apply_groove (which may be non-destructive), or the result of the operation. This incomplete picture risks incorrect tool selection or invocation.

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 compensate for the sparse schema. The one-line explanations ('The index of the track', 'The index of the clip slot') add little beyond the parameter names, with no mention of zero-based indexing, valid ranges, or the difference between session clip slots and arrangement clips.

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 'Commit groove quantization to clip notes (make it permanent)', which identifies the action and target resource. The parenthetical 'make it permanent' adds meaningful context, distinguishing it from a non-destructive preview or temporary quantization, though it does not explicitly name sibling tools.

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 gives no guidance on when to use this tool versus alternatives like apply_groove or quantize_clip. It also omits prerequisites, such as whether a groove must already be loaded or if the target clip must be a MIDI clip.

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