set_current_timecode

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

Without annotations, the description only states the basic effect (moving the playhead). It fails to disclose important behavioral details such as side effects, reversibility, error handling for invalid timecodes, or required permissions, leaving the agent with significant unknowns.

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 extremely concise, with the purpose stated in the first sentence and parameter format immediately following. Every sentence adds value; there is no unnecessary text.

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 tool's simplicity (single parameter) and the presence of an output schema (though not shown), the description covers the essential behavior and parameter format. It could mention what happens on success or failure, but it is still effective for basic usage.

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 description adds crucial meaning beyond the schema by specifying the timecode format ('HH:MM:SS:FF'), which the schema lacks (only type string). With 0% schema coverage, this provides the necessary guidance for correct parameter use.

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') and the resource ('playhead'), making it distinct from sibling tools like 'get_current_timecode' which reads the timecode. It leaves no ambiguity about what the tool does.

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 for setting the playhead to a specific timecode but does not provide explicit guidance on when to use it versus alternatives (e.g., when to use get_current_timecode instead) or any prerequisites like having a timeline open.

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