set_effect_property

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it fails. 'set' implies mutation, but the description never states intended side effects, whether a selected effect is required, whether the operation persists, what happens for invalid property names, or whether it works on audio/video/graphics effects alike. Nearly all behavioral detail is undisclosed.

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?

At eight words, it wastes no words, but brevity here stems from under-specification rather than economy: 'set effect property' is a direct restatement of the tool name with only the generic 'Premiere Pro expanded operation' prefix added. This is closer to a tautology than to efficient, information-dense copy.

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, no output schema, and zero documented parameters, this description is drastically under-specified. The tool clearly accepts a generic JSON payload (per the permissive schema), yet the description gives no hints about the payload shape, how effects/properties are addressed, or how it relates to get_effect_properties. It is inadequate for an agent to use safely.

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?

Schema description coverage is 100%, but only vacuously, since the input schema is an effectively empty permissive object with zero documented properties. The baseline of 3 applies per the high-coverage rule, and the description adds nothing beyond that baseline, offering no example structure like {effectId, property, value}. It neither helps nor hurts an agent's parameter understanding.

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 provides a clear verb+object ('set effect property') scoped to 'Premiere Pro', so an agent knows at a high level what action is being performed. However, 'expanded operation' is opaque internal jargon, and nothing differentiates this from the ~170 sibling tools like set_clip_properties, set_blend_mode, or set_time_interpolation. It never says what an 'effect property' is or how it's identified.

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 given for when to prefer this tool over the many alternatives such as get_effect_properties, apply_effect, remove_effect, or batch_apply_effect. There is no when/when-not context and no mention of prerequisites (e.g., must a clip/effect be selected, must get_effect_properties be called first). An agent could not confidently choose this tool from the description alone.

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