set_clip_opacity

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

No annotations are provided, and the description merely restates the tool name without disclosing side effects, required state, or expected outcome. It does not say whether the opacity change is destructive, whether it affects keyframes, or whether it requires a specific clip selection.

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 extremely short, which is efficient, but the prefatory phrase 'Premiere Pro expanded operation:' is vague filler that does not earn its place. The remainder simply restates the tool name.

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 mutating operation with no output schema and no annotations, the description is incomplete: it omits what input the operation expects, what state is required, and how success is reported. Given the enormous sibling list, an agent would not know which context this applies to or what arguments to pass.

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 no formal parameters and has additionalProperties:true, so there are zero declared parameters to document. Per the 0-params baseline this is acceptable, though the description could have mentioned that an opacity value is expected.

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 explicitly identifies the operation ('set clip opacity') with a clear verb and resource, so an agent knows what action is being exposed. However, it does not differentiate this from siblings like set_clip_scale or set_clip_volume beyond the name, and the 'expanded operation' prefix adds no clarity.

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?

The description provides no information about when to use this tool versus alternatives such as set_clip_scale or set_blend_mode. There is no mention of prerequisites (e.g., a selected clip), no context on whether it applies to a single clip or all selected, and no alternative routing.

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