set_start_time

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

No annotations are provided, and the description does not disclose the behavioral implications of setting the start time. For a mutation tool, important details are missing: Does this change affect the clip's position on the timeline? Is the operation reversible? What happens if the item_id is invalid? The description only states the action without any behavioral context.

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 a single, concise sentence that directly communicates the tool's purpose. Every word earns its place; there is no redundancy or filler.

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 lack of an output schema and annotations, the description is somewhat incomplete. It does not specify the scope of 'project item' (e.g., does it include clips, bins, sequences?), nor does it mention return behavior or error states. However, for a straightforward set operation with only two parameters, the description covers the core purpose adequately.

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?

Both parameters have descriptions in the schema (100% coverage), so the schema already explains them. The description adds the phrase 'timecode offset' which provides some additional context. However, it does not elaborate on the meaning of 'start_seconds' or how it relates to timecode formats, nor does it clarify what constitutes a 'project item' for the item_id. Overall, the description adds minimal value beyond the schema.

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 that the tool sets the start time (timecode offset) for a project item. It uses a specific verb ('Set') and resource ('start time' of a project item). However, it does not differentiate from the sibling tool 'set_clip_start_time', which might have a similar purpose but operate on clips rather than arbitrary project items.

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 provides no guidance on when to use this tool versus alternatives like 'set_clip_start_time' or 'move_clip'. There are no explicit context cues, such as prerequisites or conditions, that would help an agent decide to invoke this tool over others.

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