freeze_frame

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

No annotations are provided, so the description must disclose behavioral traits directly. It is nearly a tautology—'expanded operation' hints at a broad or enhanced behavior, but nothing explains what the operation does to the project, whether it modifies the timeline, whether it is destructive, or what side effects occur. The term 'expanded' is unclear and could even suggest the operation is a wrapper/kicker for other actions.

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 extremely short (one phrase), which is structurally minimal, but it is under-specified rather than concisely focused. The phrase 'expanded operation' adds noise rather than value—it is vague and could be applied to any tool. A truly concise description would state the exact action and result in a single sentence without filler.

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 tool with zero parameters and no output schema, the description is the only channel to convey context. This description is inadequate: it fails to define what 'freeze frame' means, what the operation does to the timeline or project, whether it requires a selected clip or playhead position, and how it relates to sibling tools like 'match_frame' or 'capture_frame'. The description is a placeholder rather than a specification.

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 tool has zero parameters, so the description is inherently complete with respect to parameter semantics. The baseline for zero parameters is 4, and since the schema has no property definitions, the description doesn't need to compensate. No parameter information is missing.

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 'Premiere Pro expanded operation: freeze frame.' states the resource (Premiere Pro) and a verb phrase ('freeze frame'), but the action is vague—'freeze frame' could mean capturing a still, creating a freeze frame clip, or setting a poster frame. The name 'freeze_frame' is similarly generic, and the description does not distinguish this from sibling tools like 'capture_frame', 'export_frame', or 'match_frame'.

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?

No guidance is provided on when to use this tool compared to alternatives. The description does not mention context, prerequisites, or exclusions. With dozens of sibling tools in the same domain (e.g., 'capture_frame', 'match_frame', 'set_poster_frame'), this is a critical miss.

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