set_clip_speed_qe

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, and it discloses nothing: no mention of side effects, prerequisites, what state is mutated, what 'qe' means, or what the operation returns. For a 'set' operation on a video-editing timeline, an agent has zero idea what invoking this tool will actually do.

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 short, but brevity here is under-specification rather than conciseness — its only sentence restates the name and adds no operating information. It is not front-loaded with any decision-relevant content.

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?

This is a mutating Premiere Pro tool with no annotations, no output schema, an effectively empty input schema, and a one-line tautological description amid dozens of siblings. There is nothing an agent needs to invoke it correctly — prerequisites, input format, behavior, or effect — so the definition is entirely inadequate.

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 empty except for 'additionalProperties: true', meaning the tool accepts undocumented arbitrary input, and the tool name implies a speed value must be supplied. The description adds no guidance about what parameters to pass (e.g., speed factor, target clip). Although a 0-param baseline could apply, the open schema and the semantic need for a speed value make this a real documentation gap.

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: set clip speed qe.', essentially restates the tool name verbatim and adds only a generic category label ('Premiere Pro expanded operation') that could apply to any tool in this suite. It never explains what the operation does, what 'qe' means, or how it differs from the sibling 'speed_change' tool. This is borderline tautological.

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?

The description offers no guidance on when to use this tool versus the closely related sibling 'speed_change', 'get_clip_speed', or 'set_time_interpolation'. There is no context about prerequisites (e.g., a selected clip or active sequence) and no exclusions.

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