select_clips

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

No annotations are provided, so the description carries the full burden and does not meet it. It never states whether this operation replaces the existing selection or adds to it, whether it requires an active sequence, whether it moves the playhead, or what happens if an index is out of range.

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?

A single short sentence with no waste, but its brevity comes from under-specification rather than discipline. There is no front-loaded detail beyond the bare action.

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 an undocumented optional parameter, the one-line description leaves too much for the agent to infer. It does not establish prerequisites (active sequence) or the effect on any prior selection, which matters for a state-changing UI tool.

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?

Top-level schema description coverage is 0%: the nested clip properties are documented in the schema, but the description adds nothing about the 'clips' array shape or, critically, the 'addToSelection' boolean, whose replace-vs-append semantics are left entirely undefined. The description should compensate for that gap and does not.

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 pairs a specific verb ('select') with a specific resource ('clips in the timeline'), so the agent knows this is a selection operation on timeline clips. It does not differentiate itself from close siblings like select_project_items, get_selection, or deselect_all, leaving the boundary between them implicit.

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 select_project_items (which selects items in the project panel) or get_selection, nor when to call deselect_all first. The agent has to infer that this is the timeline-only selection path.

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