set_uniform_scale

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

Annotations are not provided, so the description carries the full burden. It does not disclose whether the operation is destructive, requires a selected clip, affects only the width/height proportionally, or has any side effects. 'Expanded operation' is vague and adds no behavioral context.

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 very short, which is concise, but it lacks informative content. 'Premiere Pro expanded operation' is filler and does not earn its place. The structure is flat and does not front-load meaningful information beyond the tool name.

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?

The tool operates on a complex application (Premiere Pro) and likely requires a selected clip to apply uniform scaling. With no annotations, no output schema, and no parameter details, the description provides almost no actionable context. It fails to explain what 'uniform scale' means, how it is set, or what the outcome is.

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 formal parameters, and schema coverage is 100% (the schema is empty). The description does not explain how the scale value is provided (perhaps via a property or global state), but with no parameters to document, the baseline is 4. Since it adds no parameter-related semantics, a 3 is appropriate: average but not failing.

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 'Premiere Pro expanded operation: set uniform scale.' is minimal. It identifies the tool as setting uniform scale in Premiere Pro, but it lacks a clear verb-resource statement and does not distinguish it from siblings like 'set_scale_width_height' or 'set_scale_to_frame_size'. Purpose is implied rather than explicit.

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 about when to use this tool versus alternatives such as 'set_scale_width_height' or 'set_clip_scale'. There is no mention of context, prerequisites, or exclusions, making it ambiguous for an agent.

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