detect_scene_edits

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

No annotations are provided, so description carries full burden. It mentions optional cuts/markers (a mutating action) but does not disclose that applying cuts modifies the timeline, that detection can be time-consuming/blocking, or that it relies on current clip selection. The parameter allowUnsafeSynchronous hints at blocking but is not referenced 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?

One sentence, front-loaded with the core purpose, no redundant words. Achieves high efficiency but at the cost of behavioral depth.

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?

Adequate for a tool whose parameters are fully documented, but lacks explanation of return values/output (no output schema) and behavioral caveats like synchronous blocking. Also doesn't address the similar sibling scene_edit_detection, which could confuse selection.

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 covers 100% of parameters with descriptions, so baseline is 3. Description adds 'selected clips' context but does not elaborate on sensitivity or action enums beyond what schema provides.

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 uses specific verb 'Detects' and object 'scene changes in selected clips', clearly distinguishing from audio-based siblings like detect_silence. However, it does not differentiate from the similarly named sibling scene_edit_detection.

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?

Implied usage when scene detection is needed on selected clips, but no explicit guidance on when to prefer this over scene_edit_detection or detect_silence. The optional cuts/markers action is mentioned, but no exclusion criteria or prerequisites are given.

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