set_clip_speed_qe

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

The description discloses no behavioral traits. It does not mention whether the operation is read-only or mutates state, what effects it has on the clip, whether it requires specific permissions or conditions, or if it is reversible. With no annotations, the description carries full burden but provides nothing.

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 brief, but it fails to convey any meaningful information. The single sentence is a restatement of the tool name and does not earn its place; it adds noise rather than value. It is under-specified, not appropriately concise.

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?

Given the lack of annotations, an empty schema, and no output schema, the description is the sole source of information. It is completely inadequate: it does not explain what the tool does, its inputs, its outputs, or when to use it. The tool is essentially undocumented.

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 empty, so there are no parameters to describe. However, the tool name implies parameters are needed (e.g., clip reference, speed factor). The description does not clarify what inputs are expected or how they should be formatted, leaving the agent without guidance.

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' is tautological, merely restating the tool name without specifying what the operation does, what resources it acts on, or how it differs from similar tools like 'speed_change' or 'set_clip_speed' (if any). It provides no clear verb or resource description beyond a vague 'expanded operation' and the cryptic suffix 'qe'.

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 usage context is provided. The description does not indicate when to use this tool instead of alternatives (e.g., 'speed_change' or other clip speed-related functions). There is no mention of prerequisites, workflows, or typical scenarios.

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