set_clip_properties

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Sets Motion properties' – a terse mutation statement. It does not mention side effects, prerequisites (e.g., clip must exist), reversibility, or any special handling like coordinate conversion (which is only in the schema, not description). This is insufficient for a mutation 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 concise sentence, front-loaded with the action and resource, and contains zero filler. Every word earns its place.

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 setter with comprehensive schema and no output schema, the description is adequate but sparse. It does not mention how properties interact, whether position conversion is automatic (though schema does), or any prerequisites. Given the presence of many sibling tools and the lack of annotations, a more complete description would add context about when to use this combined setter versus individual ones.

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% with detailed descriptions for clipId and each nested property (position even includes effect controls panel conversion context). The description merely lists property names without adding new semantics, so it meets the baseline but does not exceed it.

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 verb 'Sets' and the resource 'Motion properties of a clip' with explicit property list (opacity, scale, rotation, position). It differentiates from sibling tools like set_clip_opacity, set_clip_scale, etc., which target individual properties, making this the combined setter.

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 the individual property setters (e.g., set_clip_opacity, set_clip_scale). The description implies multiple properties but never explicitly says 'use this for setting multiple properties at once' or mentions alternatives. No exclusions or prerequisites are provided.

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