set_selected_clip

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

Without annotations, the burden is on the description. It only says 'select a clip slot', but does not disclose behavior such as whether it changes the UI selection, requires an existing clip, or impacts playback. This leaves significant ambiguity.

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 very concise—one sentence with no wasted words. However, it is so terse that it sacrifices informativeness. It could be improved by adding a brief clarification on the effect of selection.

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 the context of simple parameters and no annotations, the description is incomplete. It does not mention the output schema (though one exists), error conditions, or domain-specific constraints. An AI agent would lack sufficient information to invoke it correctly without external knowledge.

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%, and the description does not add meaning beyond the parameter names. It simply restates 'by track and scene index' without explaining valid ranges, indexing bases, or the relationship to 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 the verb 'select' and the resource 'clip slot' indexed by track and scene. It is specific enough to differentiate from sibling tools like 'fire_clip' or 'set_clip_name', though it does not elaborate on the exact meaning of 'select' in the Ableton context.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, prerequisites (e.g., valid track/scene indices), or when not to use it.

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