set_uniform_scale

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

No annotations are present, so the description carries the full burden of disclosure. It says nothing about side effects, what object is modified, whether the operation is undoable, or any state changes. The agent is left completely in the dark.

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 this reflects under-specification rather than conciseness. It offers no useful information, making it a tautological restatement. While brief, it fails to earn its place by adding value.

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 complexity of the operation (likely affecting clip scaling) and the absence of a schema or output schema, the description is grossly incomplete. It omits the subject of the operation, required inputs, and any behavioral details, making it almost impossible to use correctly.

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 schema defines zero parameters but allows additionalProperties. The description fails to explain what inputs are expected (e.g., a scale factor, target clip reference). With no parameter definitions and no explanatory text, the agent cannot construct a valid call.

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' essentially restates the tool name without adding specificity about what entity is being scaled (clip, sequence, etc.) or how it differs from sibling tools like set_clip_scale or set_scale_width_height. It identifies the action but not the target resource, leaving ambiguity.

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 versus alternatives such as set_clip_scale or set_scale_to_frame_size. No context about intended invocation, prerequisites, or typical use cases is provided.

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