delete_clips

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

Implies destructiveness but provides no details on irreversibility, permissions needed, or effects on adjacent clips, gaps, or undo behavior. The ripple parameter is described only in the schema, not in the description.

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?

Single sentence is concise but overly minimal. Lacks structured information like required parameters or usage hints. Could be expanded without losing conciseness.

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 low schema coverage, the description is severely incomplete. Fails to provide essential context for correct invocation, such as what filepath refers to, how clip_ids should be formatted, or what happens after deletion.

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?

Description does not explain any parameter beyond what is in the schema. Schema has 25% coverage (only ripple has description). filepath, clip_ids, and output_path are left to inference, which may be ambiguous.

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?

Description states verb 'Delete' and resource 'clips from timeline', clearly indicating action. However, it doesn't specify that multiple clips can be deleted via the clip_ids array, nor does it distinguish between different types of clips. Still, it is specific enough for basic understanding.

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 guidance on when to use this tool versus siblings like trim_clip, split_clip, or remove_silence_candidates. Lacks context on prerequisites or scenarios where deletion is appropriate.

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