move_playhead_to_edit

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

The description indicates a state-changing action (moving the playhead), which aligns with readOnlyHint=false. No behavioral details beyond the basic action are provided, such as what happens at timeline boundaries or whether it works on all sequences. Annotations are sparse, so the description carries the burden but only gives minimal information.

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 concise sentence that clearly communicates the core functionality without any unnecessary words or fluff. It is well-structured and front-loaded.

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 the simplicity of the tool (one parameter, no output schema), the description is largely adequate. However, it could be more complete by specifying behavior at timeline edges or if no edit point exists. Overall, it covers the essential use case.

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 input schema provides a complete description of the single 'direction' parameter with its enum and default. The tool description does not add any additional meaning beyond the schema, which already achieves 100% coverage. Baseline score of 3 is appropriate.

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 clearly states the tool moves the playhead to the next or previous edit point. It uses a specific verb ('move') and resource ('playhead'), and implies the context of edit points. However, it does not explicitly differentiate from sibling tools like 'set_playhead_position' or 'get_next_edit_point', which are related.

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 provides no guidance on when to use this tool versus alternatives such as 'set_playhead_position' for absolute positioning or 'get_next_edit_point' for reading. There is no mention of when to choose 'next' vs 'previous' or any context-dependent considerations.

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