set_clip_properties

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

With no annotations, the description must disclose behavioral traits but only says 'Sets Motion properties.' It does not explain whether unspecified properties are left unchanged or reset, whether the clip must be in a sequence, or what happens on failure. 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 sentence that front-loads the verb and resource, listing properties in parentheses. It is concise and free of filler, though it lacks structure like bullet points or examples. It earns its place but doesn't go beyond a minimal statement.

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?

The tool has a nested object and multiple sibling setters, but the description offers no guidance on usage, precedence, or behavior when only some properties are provided. With no annotations or output schema, it leaves critical context unclear, especially for a mutation tool with no return value description.

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 comprehensively describes all parameters (clipId, properties, and sub-properties like position in pixels), giving 100% coverage. The description adds little beyond listing the property names already present in the schema, so it does not compensate beyond the schema baseline.

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 ('Sets') and identifies the resource ('a clip') and the specific properties (opacity, scale, rotation, position). This clearly differentiates it from single-property sibling tools like set_clip_opacity or set_clip_scale, though it doesn't explicitly state that it sets multiple properties at once.

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 instead of the individual setters (set_clip_position, set_clip_scale, etc.) or the batch variant (set_clip_properties_batch). The description lacks any context about prerequisites or scenarios, providing no help for tool selection among siblings.

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