batch_apply_effect

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about side effects, whether the operation mutates state, prerequisites (a selected sequence, active clips), or failure modes. A batch mutation tool with zero behavioral disclosure is a material gap.

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?

One sentence long, but this is under-specification, not conciseness. The clause 'expanded operation' is filler noise that earns no credit. There is no functional information being conveyed efficiently.

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?

A complex batch operation with no annotations, no documented parameters, and no output schema relies entirely on the description — which says nothing useful. The entire calling contract (inputs, effect targets, return values) is absent, so an agent must guess.

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 is an empty object with additionalProperties: true, so no parameters are actually documented despite 100% reported coverage. The description adds zero parameter information. Despite the nominal '0 params' baseline, the tool name implies it needs inputs (which effect, which target clips) that are left entirely unspecified, so an agent cannot construct a call.

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: batch apply effect' mostly restates the name batch_apply_effect. The phrase 'expanded operation' is meaningless boilerplate that adds no signal. It never says what a batch applies an effect across (clips? timeline? tracks?), and it fails to distinguish from sibling apply_effect.

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 whatsoever on when to use this tool versus the dozens of siblings (apply_effect, apply_audio_effect_to_all_clips, set_effect_property, copy_effects_between_clips). No exclusions, no prerequisites, no context for choosing it.

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