set_clip_start_time

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

The description indicates a mutation (set), consistent with readOnlyHint=false. But no additional behavioral details are disclosed, such as whether changes are reversible, affect source files, or require specific permissions. The annotations provide no extra context, leaving the agent uninformed about side effects.

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 sentences, no unnecessary words. The action is front-loaded and the explanation is direct. Every sentence contributes meaning.

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 (2 params, no output schema), the description covers the basic purpose. However, it omits usage context such as error handling, prerequisites (e.g., item must be in a project), or how it differs from similar tools like 'set_start_time'. This limits complete understanding for an AI agent.

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 100%, so the parameters are already documented. The description adds minor context: start time is a 'timecode offset' that shifts the beginning of source media, which helps interpret 'start_seconds' as an offset rather than an absolute time. This is marginal but adds some value.

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 tool sets the start time (timecode offset) of a project item, with a specific verb and resource. However, it does not differentiate from the sibling tool 'set_start_time', which may cause confusion.

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 tool versus alternatives like 'set_start_time' or other clip modification tools. No prerequisites or exclusions are mentioned.

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