timeline_detect_scene_cuts

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

Annotations already declare readOnlyHint=true, and the description's 'Analyzes the video content and returns frame numbers' is consistent with a read operation. It adds useful context beyond annotations, such as requiring Resolve 18.5+ and targeting the current timeline. No contradiction is present.

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 brief and front-loaded, with three short paragraphs. Each sentence adds value: the first gives the core action, the second explains the process, the third states a requirement, and the last describes the return. No unnecessary words or repetition.

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 zero parameters, a read-only annotation, and an output schema, the description is complete. It covers purpose, scope, a version prerequisite, and return type. No additional behavioral complexities need explanation for a tool of this simplicity.

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?

The tool has zero parameters, so the baseline is 4. There is nothing to explain about parameters; the description's mention of 'current timeline' as a scope, not a parameter, is adequate. Schema coverage is 100% by having no properties.

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 uses a specific verb and resource: 'Detect scene cuts in the current timeline.' It clearly distinguishes itself from sibling tools by focusing on the current timeline and mentions that it analyzes video content and returns frame numbers, which is a clear and unique purpose.

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 description clearly states it operates on the current timeline, which contextualizes when to use it. It also includes a version requirement ('Requires DaVinci Resolve 18.5 or later'), which is a prerequisite. However, it does not explicitly mention alternatives or when not to use it, so it lacks explicit exclusion guidance.

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