set_override_frame_rate

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

With no annotations provided, the description is the sole source of behavioral information. It fails to disclose any side effects, requirements, or consequences of setting an override frame rate. It provides no detail about what changes occur or what the user should expect.

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 concise—a single sentence—with no redundant text other than the generic 'Premiere Pro expanded operation' prefix. While it is not front-loaded with useful detail, it does not waste words.

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 any parameter complexity, the description must carry the full burden of explaining what the tool does. It fails to provide any meaningful context about the 'override frame rate' concept, its effects, or its relationship to other frame-rate settings, leaving the agent poorly informed.

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 effectively empty. According to the rubric, a 0-parameter tool gets a baseline of 4 since there are no parameter meanings to convey. The description does not need to add parameter details.

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 provides a verb ('set') and resource ('override frame rate'), but it essentially restates the tool name without explaining what 'override frame rate' means in Premiere Pro context. It does not differentiate from closely related tools like set_sequence_frame_rate or set_clip_speed, and the phrase 'expanded operation' adds no clarity.

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 guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, typical scenarios, or when not to use it. The description offers no situational context whatsoever.

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