playback_set_timecode

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

With no annotations, the description must disclose behavioral traits. It states the core action but does not mention side effects (e.g., does it stop playback?), prerequisites (e.g., an open project/timeline), or error handling for invalid timecodes. While not misleading, it leaves these aspects unaddressed.

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 concise sentence that is front-loaded with the verb 'Move' and the object. No wasted words, perfectly scoped.

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 simple setter with one well-documented parameter and an output schema, the description is adequate. It provides enough context for an agent to invoke it correctly, though it could mention prerequisites like an open timeline, but that is likely implied by the playback context.

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 for the sole parameter is 100%, with a clear description and example. The tool description adds no extra parameter semantics, so the baseline of 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?

The description clearly states the action ('Move the playhead') and the target resource ('to a specific timecode position'). It is distinct from sibling tools like playback_get_timecode, which retrieves the current timecode, making this the setter.

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 implies usage (to set the playhead to a timecode), but it does not explicitly contrast with alternatives such as playback_get_timecode or page navigation. There is no clear 'when to use' or 'when not to use' guidance beyond the obvious setter semantics.

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