set_frame_blend

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. It does not state what resources are affected, whether the operation is destructive or reversible, or any side effects. The phrase 'expanded operation' is undefined and unhelpful.

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 only one sentence, but it contains zero informative content. It is short for the sake of being short, not concise in a meaningful way. A concise description should pack information efficiently; this one simply wastes the one sentence it uses.

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?

With no annotations, no output schema, and an empty parameter schema, the description is the only source of context. It fails to explain the operation's effect, prerequisites, or relationship to sibling tools. This is completely inadequate for an agent to select and invoke the tool with confidence.

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 input schema defines zero parameters, so the baseline for this dimension is 4. The description adds no parameter information, but since there are no schema parameters to clarify, the score remains at baseline. It would have been useful to mention implicit inputs like the current clip selection, but that is more of a purpose/usage concern.

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: set frame blend' is a pure tautology that restates the tool name with a generic prefix. It does not explain what frame blending is, what it does to the clip, or how it differs from sibling tools like set_time_interpolation or set_blend_mode.

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 usage guidance whatsoever. The description does not indicate when to use this tool, what conditions are required, or which alternatives might be preferred. With many similar sibling tools, this absence of direction makes the tool very difficult to use correctly.

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