set_uniform_scale

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

With no annotations, the description carries the full burden of behavioral disclosure, but it provides none. It does not explain what 'expanded operation' entails, what state changes occur, or whether the operation is destructive or reversible.

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 one-sentence description is brief but under-specified. It omits essential context, making it not concise but merely sparse. Important operational details are missing, so the brevity does not serve a useful purpose.

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 no annotations, no output schema, and no parameter guidance, the description leaves the agent without any understanding of prerequisites, side effects, or return behavior. It fails to clarify what the operation does in the Premiere Pro context, especially in relation to sibling scaling tools.

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 per the input schema, so the description is not required to add parameter details. The baseline for 0 params is 4, and the description does not contradict or undermine this.

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 essentially restates the tool name ('set uniform scale') with a vague prefix 'Premiere Pro expanded operation.' It fails to specify the target resource (e.g., a clip, all selected clips, or a sequence) and does not distinguish itself from sibling tools like set_clip_scale or set_scale_width_height.

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 versus alternatives. The description does not mention whether a specific selection is required, whether it applies to an active sequence, or how it differs from other scaling tools.

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