set_poster_frame

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only restates the operation name. It does not explain side effects, whether the operation is destructive, what state is required, or what changes are applied.

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 very short and front-loaded, but the phrase 'Premiere Pro expanded operation' is filler that adds little value beyond the tool name. It is concise rather than informative.

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 no annotations, no output schema, and no parameter explanations, the description is insufficiently complete. An agent cannot tell what a poster frame is, what object it applies to, or what conditions must exist before calling this tool.

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 and an empty schema, so there is no parameter burden for the description to carry. The baseline of 4 applies because no parameter documentation is needed, though the description still omits contextual information that would clarify how the target is determined.

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 names a specific operation, 'set poster frame', and scopes it to Premiere Pro, so an agent can infer the basic action from the verb and resource. However, the phrase 'expanded operation' adds no concrete meaning and the description does not clarify what a poster frame is or how it differs from related operations like freeze_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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or context such as active sequence, selected clip, or playhead position. The description is only a label and does not help an agent decide when this operation is appropriate.

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