set_playhead

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds no behavioral context: it does not state whether playback is paused, whether a sequence must be loaded in the viewer, or whether this only affects ephemeral viewer state versus project data. With annotations carrying the safety burden, the description still leaves too much unstated for a state-mutating call.

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 no filler. Its brevity is appropriate for a trivial setter, though the same sentence could have carried the missing units hint without bloat.

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?

The tool mutates viewer state and takes an undefined integer, and the description covers neither prerequisites (a sequence open in the viewer) nor the meaning of 'time'. An output schema exists, so return values need not be explained, but the call itself remains under-specified.

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 0% and the single 'time' integer parameter has no description anywhere. The word 'frame' only weakly hints that 'time' is a frame index rather than a seconds value, and no range, origin, or unit is given.

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?

States a specific verb and resource: 'Move the viewer playhead to a frame.' An agent can tell this affects viewer position rather than clip data. It never contrasts with the sibling get_playhead, so the reader is not explicitly routed away from the read counterpart.

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 when-to-use or when-not guidance. It does not say to call set_playhead only after a sequence is open in the viewer, nor that get_playhead is the read-only counterpart. The agent must infer everything from the name.

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