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 of explaining behavior. It only states 'get clip speed' without mentioning side effects (if any), required context (e.g., active selection), return format, or error conditions. The read-only nature is implied but not explicitly disclosed.

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 short but wastes space with the generic phrase 'Premiere Pro expanded operation' and fails to include any substantive explanation. It is under-specified rather than genuinely concise, since it leaves critical details unaddressed.

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 absence of annotations, output schema, and parameter details, the description is the sole source of information. It fails to explain what 'clip speed' refers to, how the target clip is determined, or what the output represents. Simple as the operation may be, the description is not adequate for an agent to reliably use it.

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 accepts zero parameters, so there is no parameter semantics to clarify. The schema covers everything vacuously, and the description adds no parameter information, which is acceptable for a no-parameter tool.

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 identifies the action as retrieving clip speed ('get clip speed'), which is a specific verb and resource. However, 'Premiere Pro expanded operation' adds little and there is no explicit distinction from sibling getters like get_clip_properties, though the intent is clear.

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, what conditions apply, or how it differs from alternatives like set_clip_speed_qe or speed_change. No context or examples are provided, leaving the agent without any selection criteria.

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