screenstudio_editor_seek

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

Annotations declare readOnlyHint=false and destructiveHint=false, with no open world, so the safety profile is partly covered. But the description doesn't explain the effect of seeking (does it pause playback? require an open project?) or the interaction between the two optional time parameters. Little context beyond the annotations.

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 and compact, but so terse that it omits important qualifiers. It is minimally acceptable in size but not richly structured.

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 an editor mutation with no output schema and zero parameter documentation, the description is too thin. It omits prerequisites (open project), precedence of sourceMs vs playbackMs, and any effect on recording state, leaving gaps for an agent to call it correctly.

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 0% for three parameters, so the description must compensate. It only vaguely mentions 'playback or source time' and does not clarify units (schema hints ms), precedence when both are supplied, or that projectPath is required.

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 ('move') and resource ('editor playhead') with the target ('playback or source time'). It clearly describes the action, though it doesn't distinguish itself from siblings like editor_frame or editor_play beyond the time axis.

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 guidance on when to use this versus alternatives such as screenstudio_editor_frame or screenstudio_editor_play. An agent is left to infer that seek sets the playhead without playing.

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