detect_scene_edits

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

With no annotations, the description must disclose behavior on its own. It mentions optional cuts or markers, but does not warn about potential blocking, synchronous execution, the async/sync behavior referenced by allowUnsafeSynchronous, effects on the timeline, or whether detection without an action is read-only. This leaves significant behavioral risk undisclosed.

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?

A single, front-loaded sentence communicates the core operation without wasted words. However, it is slightly under-specified for the tool's complexity, which prevents a full 5.

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 no output schema, no annotations, and a 5-parameter tool, the description is incomplete. It does not explain what the tool returns, whether it blocks, what happens with no selected clips, or whether markers/cuts replace or append to existing content. The agent is left to infer critical invocation behavior.

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 baseline applies. The description adds little beyond the schema, though the phrase 'optionally adds cuts or markers' loosely maps to the action enum and offers some semantic reinforcement. No parameter details or formats are added.

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 a specific action (detects scene changes) on a specific resource (selected clips) with an optional outcome (cuts or markers). This is clear and distinct from silence detection, though it doesn't explicitly differentiate itself from the similarly named 'scene_edit_detection' sibling.

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 about when to use this tool versus alternatives. The description implies usage when scene changes are needed, but it never states prerequisites (e.g., clips must be selected) or when to prefer the sibling scene_edit_detection tool.

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