set_blend_mode

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

No annotations are provided, and the description discloses no behavioral traits whatsoever. It does not mention scope, side effects, prerequisites, expected state changes, or what happens after invocation, leaving the agent completely uninformed.

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 short but severely under-specified. The phrase 'Premiere Pro expanded operation' is meaningless filler, and the rest simply repeats the tool name. This is not concise completeness; it is absence of specification.

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 setter tool with no annotations, no output schema, and an empty parameter schema, the description is the sole source of behavioral information. It provides almost none, making the tool non-discoverable and unsafe to invoke correctly.

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?

There are zero declared parameters, so per the rubric baseline is 4. The schema's loose additionalProperties offers no parameter names or types, and the description does not clarify how the blend mode value should be supplied, but with no explicit params the schema imposes no burden the description must overcome.

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 merely restates the tool name ('set blend mode') with the filler phrase 'Premiere Pro expanded operation,' providing no actual information about what the tool does, what a blend mode is, or how it differs from related siblings like set_frame_blend or set_time_interpolation.

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 given about when to use set_blend_mode versus alternatives, when not to use it, or any prerequisites. The sibling list includes many similarly named setter tools, but the description offers no differentiation.

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