set_timeline_time

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the description's marginal burden is lower. The description adds the return shape but does not explain what editor state is affected or why the mutation is flagged destructive, leaving some behavioral gaps.

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?

Two short lines with zero filler; the purpose sentence is front-loaded and the return shape is appended compactly. Every element earns its place.

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?

With no output schema present, the description usefully inlines the return object (requested_time vs actual_frame, time_set), compensating for that gap. It is close to complete for a simple setter, though it could note behavior when the editor is closed or time is out of range.

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 description coverage is 100%, so both parameters (time in seconds >= 0, sequence_name) are already documented. The description adds no syntax or format detail beyond the schema, 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?

States a specific verb (set) and resource (playhead time) scoped to 'the open Sequencer editor on a target sequence', which is more precise than a bare tautology. The 'open Sequencer editor' framing implicitly separates it from the runtime sibling set_level_sequence_time_runtime, but it does not name that alternative explicitly.

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 phrase 'open Sequencer editor' implies a precondition and usage context (editor-side playback scrubbing), which is useful. However, there is no explicit when-to-use/when-not-to-use statement and no reference to the runtime alternative it competes with.

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