Adjust a Premiere Pro clip's opacity to control transparency and blending with underlying video tracks.
Premiere Pro expanded operation: set clip opacity.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "set_clip_opacity"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for disclosing behavior. It only mentions 'expanded operation' without describing what happens, side effects, or requirements (e.g., needing a selected clip). This is severely under-specified.
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 not well-structured; it's just a fragment ('expanded operation') that adds no value. It's concise but not informative, and the phrase feels like placeholder text.
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?
Even though the operation has no parameters or output schema, the description should at least specify the target (e.g., the selected clip) or any side effects. It provides none, making it incomplete for safe and correct usage.
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 has zero parameters, so there is nothing to document. The description adds no semantic meaning beyond the empty schema. While baseline for 0 params is 4, the description contributes nothing, so a 3 is appropriate.
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 clip opacity' essentially restates the tool name. It identifies the resource (clip opacity) but 'expanded operation' is vague and doesn't differentiate from sibling property setters like set_clip_volume or set_clip_scale, which are equally self-explanatory.
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 the many alternative property-setting tools. There is no mention of prerequisites such as selecting a clip, or any context that would help an agent decide when to invoke this operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.