set_playhead

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing beyond the bare action. It doesn't state which sequence is affected, whether playback state changes, or whether an open project/active sequence is required.

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?

Four words, front-loaded, with no filler or repetition. It is efficiently structured, though the brevity reflects under-specification captured in the other dimensions rather than optimal sizing.

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 no-annotation, no-output-schema mutation tool in a crowded timeline family, the description should at least identify the target sequence and any precondition. As written, an agent knows only the verb and must infer everything operational.

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 coverage is 100% and the single parameter is already documented as "Seconds" with a non-negative minimum. The description adds no additional meaning such as frame alignment, timebase handling, or range clamping, so the baseline 3 applies.

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?

"Move the playhead" gives a specific verb and resource, so an agent can tell this is a timeline position mutation. It does not distinguish itself from nearby siblings such as get_playhead (the read counterpart) or go_to_edit, which likely also repositions the playhead.

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?

There is no guidance on when to use this versus go_to_edit, play, stop, or get_playhead. The description also omits prerequisites such as needing an active sequence or open project, leaving routing entirely to inference from the name.

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