set_keyframe_interpolation

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

With no annotations provided, the description carries the full burden. 'Premiere Pro expanded operation' is uninformative and does not disclose any behavioral traits such as whether the operation is destructive, requires clip selection, or affects which keyframe. This is a significant transparency 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?

The description is a single short sentence, which is efficient. However, 'expanded operation' is filler that adds no meaning, and the sentence could be more precisely worded as just 'Set keyframe interpolation.'

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 with no annotations, no output schema, and an empty input schema, this description is inadequate. It does not explain what keyframe interpolation entails, how it relates to keyframes, or what the agent must provide. The context is too sparse for reliable invocation.

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% per context, but the schema defines no properties and permits arbitrary additional properties. The description adds no parameter semantics—it does not explain what values are needed (e.g., keyframe index, interpolation type). Baseline 3 applies given the schema coverage, but the description fails to compensate for the empty schema.

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 uses a specific verb + resource: 'set keyframe interpolation.' It clearly indicates the operation's target, though 'expanded operation' is vague jargon. It does not distinguish from siblings like set_time_interpolation, but the core purpose is stated.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage from the name alone among many sibling tools.

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