freeze_frame

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

With no annotations, the description must disclose behavioral traits but only states that the tool exports and re-imports a still. It does not specify where the still is imported (e.g., timeline, bin), whether it overwrites existing files, undo behavior, or any required permissions. The vague 'imports it back' leaves significant behavioral uncertainty.

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, front-loaded sentence that efficiently conveys the core action. It avoids redundancy but could benefit from additional structure to separate the export and import phases.

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 lack of annotations and output schema, the description is incomplete. It does not explain the result of the import (e.g., added to timeline at playhead), prerequisites (e.g., an active sequence or selected clip), or how the tool integrates with other workflow steps. For a tool that modifies the project, more context is needed.

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 each parameter described. The description adds no new semantics beyond the schema; it merely implies the use of time_seconds. Given the baseline of 3 for complete schema, the description does not enhance parameter understanding further.

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 specifies the action ('Create a freeze frame'), the source ('from a clip at a specific time'), and the dual outcome ('Exports the frame and imports it back as a still image'). This effectively distinguishes it from siblings like capture_frame (which captures the playhead without re-import) and export_frame (which only exports).

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?

The description does not provide guidance on when to use this tool versus alternatives such as capture_frame or export_frame. It lacks explicit statements about context, prerequisites (e.g., a clip must be selected or a sequence open), or situations where other tools would be more appropriate.

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