scene_edit_detection

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

No annotations are provided, so the description carries the full behavioral burden. It states that detection operates on selected clips and can optionally mutate the timeline, but it omits permissions, whether changes are undoable, what happens when no cuts are detected, and how the operation affects linked audio beyond the schema flag.

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. The detection purpose comes first, followed by the optional actions, making it 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?

For a timeline-mutating tool with no annotations and no output schema, the description is too thin. It does not explain selection prerequisites, what the tool returns or reports, or how the optional actions interact with existing clips, markers, or subclips.

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 100%, so the parameter meanings are already documented in the schema. The description restates the action outcomes at a high level and implies operation on selected clips, but adds no detail about sensitivity or linked-audio behavior beyond the 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 gives a specific verb and resource: detect scene changes/cuts in selected clips. It also names the optional outcomes (apply cuts, create markers, create subclips). It is clear but does not explicitly distinguish itself from adjacent tools like razor_clip, add_marker, or create_sub_clip.

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 is given on when to use this tool rather than manual razor_clip or marker workflows, nor on prerequisites such as requiring an active selection. The optional actions are listed but not framed as a decision guide.

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