set_clip_start_time

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

The description only restates that the operation sets a clip start time; it does not disclose whether the change is destructive, whether it affects linked clips, whether it requires a selection, or whether it returns any result. With no annotations provided, the description carries the full burden and fails to provide useful 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 short, but this is under-specification rather than genuine conciseness. It contains no front-loaded useful context beyond restating the tool name, so the brevity does not serve the agent.

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?

The definition is missing nearly everything an agent would need: the meaning of 'expanded operation', whether a clip must be selected, what time format to use, what effect the operation has on the timeline, and what the return value is. Given the large sibling tool set and absent annotations/output schema, this is not a viable standalone definition.

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?

Although the context reports zero parameters, the schema is an empty object with additionalProperties: true, so the actual argument surface is entirely unspecified. The description does not name a time parameter, a clip identifier, or any other input, leaving the agent without enough information to invoke the operation correctly.

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 is essentially a restatement of the tool name: 'set clip start time' adds no new information beyond the name itself. The 'Premiere Pro expanded operation' prefix is generic and does not explain what makes this operation 'expanded' or how it differs from related tools like set_start_time or trim_clip.

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?

There is no guidance about when to use this tool versus alternatives, no mention of prerequisites such as a selected clip or a target timeline, and no statement about what state the sequence must be in. 'Expanded operation' is a label, not a usage condition.

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