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, but it reveals nothing beyond the name. It does not mention required state, parameter side effects, undoability, or what happens on failure. 'Set' implies mutation, but no meaningful behavior is disclosed.

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 efficient clarity. The phrase 'expanded operation' is filler and the sentence adds no useful structure beyond 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 tool that must accept at least some effect/property/value specification, the description and schema are completely inadequate. There is no indication of required arguments, return behavior, or prerequisites, leaving an agent unable to invoke it.

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 is an empty object with additionalProperties true, so any parameters are allowed but none are described. The description provides zero information about which effect, which property, or what value should be supplied, making it impossible to call the tool correctly.

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 'set effect property' essentially restates the tool name and adds only the generic context 'Premiere Pro expanded operation,' which conveys no specific behavior. It provides no differentiation from sibling tools like get_effect_properties or remove_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?

There is no guidance about when to use this tool, what must be set up first (e.g., selected clip or effect), or how it relates to alternatives. The description simply announces what the tool does without any context for selection.

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