set_override_frame_rate

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

There are no annotations, so the description must disclose behavior. It merely restates the tool's name and adds the generic label 'expanded operation', offering no information about side effects, prerequisites, or how the override interacts with other settings. This is essentially a tautology.

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 brief and front-loaded, but the phrase 'Premiere Pro expanded operation' adds no meaningful information and could be omitted. It is concise but under-specified, veering into vagueness rather than efficient clarity.

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?

With no annotations, no output schema, and zero parameters, the description is the only source of context. It fails to explain what 'override' means, the effect on the sequence or clip, or any constraints. The tool is left entirely unclear despite being a simple setter.

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 schema shows no required or optional inputs. With 0 parameters, the baseline is 4, and there is nothing for the description to add beyond what the schema already indicates.

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 tool as setting an override frame rate, using a specific verb+resource construction. It distinguishes from siblings like set_sequence_frame_rate by including 'override', but it does not explicitly compare to any sibling tool.

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 provided on when to use this tool rather than alternatives such as set_sequence_frame_rate or set_override_pixel_aspect_ratio. The phrase 'expanded operation' is vague and does not convey any usage context.

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