set_current_time

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

With no annotations, the description carries the full behavioral burden, but it only says 'Move the playhead.' It does not disclose whether this requires an active timeline, whether the timecode must be within project bounds, or what happens if the timecode is invalid.

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 front-loaded sentence with no padding. It is appropriately sized for a simple setter, though the terseness leaves behavioral gaps that a slightly richer sentence could address.

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 mutation tool with no annotations, no output schema, and an undocumented parameter, the description is too thin. It gives an example timecode but omits required context such as active-timeline assumptions and the effect of moving the playhead.

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%, so the description should compensate. The example '01:00:10:00' usefully demonstrates the HH:MM:SS:FF timecode format, but it does not describe frame-rate or drop-frame handling, bounds, or other constraints on the single timecode parameter.

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 states a specific action and target: moving the playhead. This is clear for a video-editing context, though it does not explicitly contrast with the sibling get_current_time. The example timecode clarifies the intent is to set the current position, not read it.

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 get_current_time or set_current_timeline. No prerequisites or exclusions are stated, leaving the agent to infer that an active timeline/project is required.

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