set_scale_to_frame_size

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 discloses nothing beyond the operation name. It does not state side effects, selection requirements, whether it resets existing scale values, or what the result is for the user.

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 short but under-specified. It is not concise in a helpful sense; it simply rephrases the tool name and omits context that could be provided in a sentence or two.

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?

For a parameterless operation with no annotations and no output schema, the description is incomplete because it fails to state what clip or sequence the operation applies to, whether it is destructive, or how the agent should confirm success. An agent cannot safely invoke this tool based solely on the provided text.

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, so the empty schema already fully describes the signature. The description adds no parameter-level detail, but none is needed; the baseline for 0 parameters is appropriate.

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 restates the tool name verbatim ('set scale to frame size') with no additional explanation of what the operation does or what object it affects. It adds only the generic phrase 'Premiere Pro expanded operation,' which does not distinguish it from siblings like set_clip_scale, set_scale_width_height, or set_uniform_scale.

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 the many similar scale-related sibling tools. The agent is given no context about prerequisites, such as whether a clip must be selected or an active sequence must exist.

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