get_clip_speed

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

No annotations are provided, so the description carries the full burden. The word 'get' implies a read operation, but the description does not disclose side effects, whether a clip must be selected, how the target clip is determined, or what the returned value represents. This is minimal and under-specified for a tool with no annotation safety profile.

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 very short and front-loaded, containing no filler sentences. The phrase 'Premiere Pro expanded operation' is somewhat redundant given the sibling context, but the description remains concise and easy to parse.

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 getter with no annotations and no output schema, the description should clarify which clip is referenced, what context is required, and what the returned speed value represents (e.g., ratio, percentage). None of this is present, so an agent lacks important information needed to use the tool correctly.

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 tool has zero parameters, so the description does not need to explain parameter behavior. The empty schema is unambiguous in this respect, and the baseline for zero-parameter tools applies.

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 states a clear verb and resource: 'get clip speed'. This tells an agent the tool reads speed information for a clip. However, it does not distinguish this from related siblings like get_qe_clip_info or get_clip_properties, and the phrase 'expanded operation' adds little.

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 on when to use this tool versus alternatives such as set_clip_speed_qe, speed_change, or get_qe_clip_info. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage entirely from the name.

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