remove_clip

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

With no annotations provided, the description carries the full behavioral burden. "Ripple-delete" usefully signals that downstream timeline content shifts, but the description does not state that the operation is destructive/irreversible, what permissions are required, or what happens to effects or overlays on the removed clip.

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 front-loaded sentence with no filler. It is efficient, though its brevity contributes to the missing operational details noted elsewhere.

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 destructive timeline mutation with no annotations, no output schema, and 0% parameter documentation, the description is too sparse. It discloses the ripple behavior but omits reversibility, permissions, return behavior, and how the clip is targeted.

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%, so the description must explain the two required parameters. It does not mention producer_id or project_name at all, and notably the schema exposes no explicit clip identifier, so the agent is left without guidance on how the target clip is identified.

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 gives a specific verb and resource: "Ripple-delete one clip from the timeline." This is clear and distinguishes deletion from operations like trim_clip or split_clip, though it does not explicitly contrast with the close sibling remove_segment.

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 phrase "one clip" provides some scope, but the description gives no explicit guidance on when to use this tool instead of remove_segment, trim_clip, or split_clip. There are no stated prerequisites or exclusions for an agent to follow.

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