Set Clip Properties

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

Annotations already declare the safety profile (non-readonly, non-destructive, non-idempotent), so the bar is lower. The description adds real behavioral context: it discloses a read-back of each requested value, and that speed 'fails before mutation' (i.e. no partial write), which is valuable for error/recovery reasoning.

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?

Two sentences, zero padding, front-loaded with the supported capability before the unsupported case and its alternative. Every clause 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?

An output schema exists, so return values need not be explained, and the 7-param schema is fully documented. The only missing piece is disambiguation against the single-property setter siblings, which slightly limits completeness.

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 description coverage is 100% and the speed parameter's unsupported note is already in the schema, giving a baseline of 3. The description reinforces the supported-property set and the failure semantics for speed, adding marginal meaning beyond the schema.

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?

States a specific verb (Set) plus the exact resource and enumerates the supported property set (opacity, scale, position, rotation). An agent immediately knows this is a multi-property mutation on a clip, distinct from single-property or duration tools.

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?

Explicitly handles the speed edge case and routes to set_clip_duration. However, it never addresses the granular siblings set_clip_scale, set_clip_opacity, set_clip_rotation, and set_clip_position, so the agent cannot tell from the description whether to batch here or call those instead.

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