capcut_set_clip_transform

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

Annotations are absent, so the description carries the full behavioral disclosure burden. It says 'adjusts' but does not clarify whether values are absolute or cumulative, whether unspecified properties remain unchanged, or whether prior transforms/keyframes are affected. This ambiguity is significant for a mutating tool.

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 front-loaded sentence with no filler. Every word earns its place: the verb, target resource, and the affected transform properties are all immediately visible.

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 mutating tool with no annotations and no output schema, a one-sentence description is thin. Missing context includes absolute vs relative semantics, behavior of omitted parameters, and what the agent can expect as a success signal or result. The complete parameter schema helps but does not resolve these behavioral gaps.

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 schema already documents all parameters and their ranges/units. The description maps broad categories (scale, rotation, position, opacity) onto the schema, but adds no new meaning beyond what the structured input already provides.

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 uses a specific verb ('Adjusts'), names the resource ('an existing clip'), and lists the exact transform properties (scale, rotation, x/y position, opacity). This clearly distinguishes it from transform-related siblings like capcut_set_clip_speed or capcut_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?

No guidance is given about when to use this tool versus alternatives such as capcut_add_keyframe for animated transforms or capcut_set_clip_speed for speed adjustments. The only implied usage is that the clip must already exist, but this is not stated as a decision rule.

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