freeze_frame

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

The description discloses the key composite behavior: exporting and importing back as a still image. This adds value beyond the sparse annotations (readOnlyHint=false, destructiveHint=false). No contradictions.

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 two concise sentences, front-loaded with the action, and contains no unnecessary words. Every sentence 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?

The description covers the main workflow (export and import) and the three parameters are well-described in the schema. However, it lacks details like prerequisites (e.g., active sequence) or where the imported still appears in the timeline. Still mostly complete given the tool's moderate complexity.

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%, so baseline is 3. The description adds context by explaining that the frame is imported back, linking the output_path to the exported frame and clarifying the purpose of time_seconds and duration_seconds. This provides meaningful context above 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?

The description clearly states the action ('Create a freeze frame'), the resource ('from a clip at a specific time'), and the outcome ('Exports the frame and imports it back as a still image'). It distinguishes itself from siblings like 'export_frame' by emphasizing the import-back behavior.

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 implies usage for creating a freeze frame, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'export_frame' or 'capture_frame'). No when-not-to-use or context is mentioned.

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