set_clip_scale

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

No annotations are provided, so the description must carry the burden of disclosing behavior. It does not state whether this operation modifies clip properties, requires a selection, has side effects, or returns any result. It offers no behavioral context beyond the verb 'set'.

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 extremely short, but brevity here is under-specification rather than conciseness. It is a single sentence that adds no information beyond the tool name. Every useful detail is absent, so the structure fails to convey meaning efficiently.

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 large set of sibling transformation tools (set_uniform_scale, set_scale_width_height, set_clip_position, etc.), this tool's purpose is highly ambiguous. There is no output schema, no parameter documentation, and no behavioral description. An agent cannot determine what this tool accepts or what it accomplishes, making it nearly unusable.

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 has no defined parameters but allows additionalProperties, implying parameters are expected but undocumented. The description gives no hint about what parameters should be passed (e.g., scale value, clip reference). With zero parameter semantics provided, an agent cannot know how to invoke the tool 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 'Premiere Pro expanded operation: set clip scale' merely restates the tool name with a vague prefix. It does not specify what 'scale' means (uniform, width/height, scale-to-frame), which clip it applies to, or how it differs from siblings like set_uniform_scale or set_scale_width_height. This is essentially a tautology.

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 on when to use this tool versus alternatives such as set_uniform_scale, set_scale_width_height, or set_scale_to_frame_size. There is no mention of prerequisites, target selection, or expected context. The description provides no actionable usage direction.

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