set_clip_scale

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

With no annotations, the description carries the full burden. It does not disclose whether the operation is safe or destructive, what happens if the clip lacks a Motion effect, or any permissions needed. The default assumption is mutation, but side effects are unstated.

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, clear sentence. It is appropriately concise for a simple property-setter tool. No redundant or wasted words.

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 tool's simplicity (2 params, no output schema), the description covers the essential point. It implies the clip must have a Motion effect, which is a useful constraint. However, it could be more complete by noting that the scale applies only to the Motion effect and not other effects.

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 already provides descriptions for both parameters (node_id and scale) with examples (100 = original size). The description adds no new information beyond what the schema offers. Baseline 3 is appropriate given 100% schema coverage.

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 clearly states the action: setting the Scale property on the Motion effect of a video clip. It specifies the verb ('Set'), the resource ('Scale property'), and the context ('video clip's Motion effect'). However, it does not differentiate from sibling tools like set_clip_properties or set_scale_to_frame_size, which could also influence scale.

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 on when to use this tool versus alternatives (e.g., set_clip_properties for setting multiple properties at once, or set_scale_to_frame_size for a different scaling mode). There are no contextual hints or exclusions.

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