set_clip_scale

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

With no annotations, the description carries full responsibility for behavioral disclosure, but it reveals nothing: no units, no mutation effect, no selection requirements, and no semantics for how scale is applied. 'Expanded operation' is ambiguous and unhelpful.

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 one sentence, but it is under-specification rather than concise: the first half is filler and the second merely restates the tool name. It has no information density.

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 no-parameter mutating tool with no annotations and no output schema, this description is far too sparse. It fails to explain what 'clip scale' means, which clip is affected, or how it interacts with the many scale-related sibling tools.

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 tool has zero parameters, so the schema coverage is trivially complete and there is no parameter meaning the description must add. The baseline of 4 applies because no parameter documentation burden exists.

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 restates the tool name exactly: 'set clip scale.' 'Premiere Pro expanded operation' is generic filler and does not differentiate this tool from siblings like set_scale_to_frame_size, set_uniform_scale, or set_scale_width_height.

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 provided about when to use this tool versus alternatives. It also does not mention prerequisites such as having a clip selected or any exclusion cases.

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