remove_all_effects

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

No annotations are provided, so the description alone must disclose behavioral traits. It only states the action 'remove all effects' without explaining whether it modifies the selected clip, requires an active sequence, affects audio and video effects, is undoable, or has other side effects. This is a significant transparency gap for a destructive operation.

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, but brevity here is under-specification rather than effective conciseness. The opener 'Premiere Pro expanded operation' does not earn its place, and the rest simply restates the tool name without adding useful structure or context.

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 zero-parameter, destructive operation with no annotations and no output schema, the description carries the full burden of explaining context. It fails to state the target scope, selection requirements, or any behavioral caveats, leaving an agent unable to confidently decide how to invoke the tool 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?

The tool has zero parameters and the input schema is an empty object with 100% coverage, so the baseline is 4. The description adds no parameter-specific meaning, but none is necessary since the schema already fully represents the parameter surface.

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 names the action and resource: 'remove all effects.' However, it does not specify what the effects are removed from—selected clips, the active sequence, or the entire project. The phrase 'Premiere Pro expanded operation' adds category flavor but no operational detail, so the purpose is only vaguely defined beyond the tool's name.

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 guidance about when to use this tool versus alternatives. Sibling tools like remove_effect, remove_effect_by_name, and copy_effects_between_clips exist, but the description does not clarify whether this tool should be used for a single clip, multiple clips, or the whole sequence, nor does it mention any prerequisites such as having a selection active.

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