set_clip_opacity

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

No annotations are present, so the description carries the full burden. It offers essentially nothing beyond the tool name—no mention of which clips are affected, whether a selection is required, whether changes are keyframable, or any side effects. The phrase 'expanded operation' is vague and unexplained.

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?

It is a single concise sentence with no wasted words, but the prefix 'Premiere Pro expanded operation:' adds little value and could be omitted. Overall, it is efficient but not optimally structured for clarity.

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 mutation tool with no annotations and no output schema, the description is far too thin. It omits critical context such as how the clip is identified, the expected value range, and whether the operation is reversible. It barely meets the minimum for understanding the tool's function.

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 schema declares zero parameters, so the baseline is 4, but the description fails to clarify how the opacity value or target clip is passed, especially since the schema permits arbitrary properties. The description adds no parameter information to compensate for this ambiguity.

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: set clip opacity in Premiere Pro. The verb-resource pairing is specific, and the property name distinguishes it from sibling clip property setters, though it doesn't elaborate on scope.

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 versus other clip property setters, nor any context about prerequisites, target selection, or alternatives. The description simply restates the function without positioning it among the many sibling set_* tools.

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