set_clip_rotation

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Set clip rotation' implies a mutation of clip state, but the description does not disclose side effects, whether rotation is applied to selected clips or a specific clip, units, or reversibility. It provides almost no behavioral context beyond the verb itself.

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 and front-loaded with the operation, which is structurally clean. However, the 'Premiere Pro expanded operation:' prefix is boilerplate and largely redundant given the tool name and sibling context. It is concise but doesn't use the available space to add meaningful information.

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 a state-mutating tool with no annotations and no output schema, the description is too sparse. It fails to mention what clip is affected, whether the operation requires a selection, what rotation value/unit is expected, or what the result will be. Even a simple setter benefits from stating the target context and expected input, especially in a large sibling tool set.

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?

The input schema declares zero properties, and the schema description coverage is 100%, so the description is not obligated to document parameter details. Baseline for a zero-parameter tool is 4. The additionalProperties: true schema allows arbitrary properties but provides no definitions, and the description offers no clue about expected value names, though with zero declared parameters this is not a major penalty.

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: 'Premiere Pro expanded operation: set clip rotation.' It names an action and resource but adds no detail about what rotation means, how it is applied, or what distinguishes it from sibling set_clip_* tools. The boilerplate 'Premiere Pro expanded operation' prefix does not improve purpose clarity.

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 on when to use this tool versus alternatives such as set_clip_position, set_clip_scale, or set_clip_anchor_point. No prerequisites (e.g., a selected clip) or context for when rotation should be set are provided. The description is purely declarative and leaves usage entirely to inference.

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