lift_selection

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

The description explains that the tool removes content without closing the gap, which adds context beyond annotations. However, annotations include destructiveHint=false, but the tool mutates the timeline, creating a contradiction. The description itself is clear, but the annotations are misleading.

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 concise sentence that efficiently communicates the tool's action. It could be structured with more explicit enumeration of use cases, but it remains clear and to the point.

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?

For a zero-parameter tool, the description adequately covers the operation's purpose and input scope. It explains both relevant triggers (in/out points or selected clips) and the behavioral nuance of not closing the gap. No output schema exists, so no return value details needed.

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 schema provides no parameter details. The description compensates by specifying what content is lifted (between in/out points or selected clips), adding meaningful context beyond the empty 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 verb 'lift' and specifies the resource as 'content between sequence in/out points or selected clips'. It distinguishes from extract by noting 'without closing gap', so the purpose is specific and unambiguous.

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?

The description mentions the behavior 'remove without closing gap' but does not provide explicit guidance on when to use this tool versus alternatives like extract_selection or ripple_delete. It leaves the agent to infer usage without direct comparison.

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