apply_groove

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to describe the effect of applying a groove (e.g., timing alterations), whether it is destructive/reversible, or any side effects on the clip. This is a significant gap for a mutation tool.

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 well-structured. It front-loads the purpose in a single sentence, then lists parameters in a clear bullet-style format. Every sentence adds value without redundancy.

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?

Despite complete parameter coverage, the tool lacks behavioral context, usage guidance, and any note on return values or state changes. As a mutation tool with no annotations or output schema, it should explain more about what 'apply' entails and when to use it. The description is minimal and leaves the agent to fill in critical gaps.

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?

The schema provides only parameter names and types (0% coverage), so the description compensates by explaining each parameter: track_index (track), clip_index (clip slot), groove_index (groove pool). This adds necessary semantic meaning beyond the structured 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?

The description clearly states the tool's action: 'Apply a groove to a clip.' This is a specific verb+resource construction that distinguishes it from siblings like commit_groove or get_groove_pool. There is no ambiguity about what the tool does.

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. It does not mention prerequisites (e.g., existing clip, groove pool availability) or when not to use it. The description simply states the operation without contextual selection criteria.

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