get_clip_speed

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

With no annotations, the description carries the full burden, but it provides no behavioral details. It does not disclose what is returned (e.g., speed as a float, units), whether it operates on the selected clip, or any side effects or requirements. Minimal behavioral transparency is given.

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 sentence but essentially restates the tool name ('get clip speed') and adds the vague prefix 'Premiere Pro expanded operation'. This under-specification does not earn its place; it is too terse to be helpful.

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?

As a getter with no annotations or output schema, the description leaves critical context unexplained. It does not specify what input it uses (e.g., current selection), what it returns, or how it behaves, making it incomplete even for a simple tool.

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, and the input schema is essentially empty. The baseline for zero parameters is 4, and while the description doesn't add param-related meaning, there are no parameters to describe.

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 clearly uses 'get' + 'clip speed' as the verb and resource, making the tool's purpose obvious. However, it does not explicitly distinguish it from sibling tools like 'set_clip_speed_qe' or 'speed_change', though the name is fairly unique.

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, nor any mention of prerequisites (e.g., a selected clip). The description simply states what it does without contextual usage information.

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