select_clip

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

With no annotations and no description of behavioral traits, the tool's side effects are undisclosed. It does not state whether selection changes the UI, what happens to previous selections, or whether any permission is required. The description carries the full burden but provides zero transparency.

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, followed by a parameter list. It is appropriately sized, though the parameter list duplicates the schema. No unnecessary words or fluff.

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?

The tool is simple, but the description lacks critical context: what 'select' actually does in the DAW, how to construct valid indices, and how selection relates to other clip operations. There is no output schema or annotations to fill the gap, leaving the description incomplete for an agent needing to invoke 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?

The description provides explanations for both parameters—'index of the track containing the clip' and 'index of the clip slot'—which adds meaning beyond the bare schema names. However, it omits details like zero-based indexing or range constraints, leaving some ambiguity.

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 function: 'Select a clip slot,' which is a specific verb+resource combination. It distinguishes from sibling tools that fire, stop, get, or set clips by using the distinct action 'select.' However, it does not explicitly differentiate from other select-type tools like select_track or select_scene.

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?

There is no guidance on when to use this tool versus alternatives. No context is provided about prerequisites, such as whether the track and clip must already exist or be visible, nor is there any mention of when selection is needed versus other clip operations.

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