deselect_all_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 of disclosing behavior. It only says 'deselect all clips' without mentioning whether this affects only the active sequence, all sequences, or the current selection context. There is no indication of whether the operation is reversible, if it requires specific permissions, or if it has any side effects on other project state. This is minimal disclosure.

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 a single sentence with no filler or redundancy. It is front-loaded and immediately communicates the core action. For a tool with no parameters and a straightforward operation, this level of conciseness is appropriate and efficient.

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 simplicity of the tool (no parameters, no output schema), the description is minimally sufficient. However, it lacks any context about the scope of the operation (e.g., active sequence vs. whole project) and does not mention potential side effects or related operations. The phrase 'expanded operation' hints at being part of a larger set but does not explain. Overall, it is adequate but not comprehensive.

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 tool has zero parameters, so the baseline is 4. The schema's parameter coverage is 100% (vacuously true), and the description adds no parameter information beyond what the input schema already indicates (empty object). No additional meaning is needed since there are no parameters to describe.

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 action: deselect all clips. It identifies the resource (clips) and the operation (deselect all). However, it does not differentiate from sibling tools like select_all_clips or select_clips_by_name, which are related but opposite operations. The phrase 'expanded operation' is vague and does not add clarity.

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 such as select_all_clips or invert_selection. The description does not mention any prerequisites, side effects, or typical use cases. It merely states what it does without context, leaving the agent to infer when it might be appropriate.

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