set_clip_scale

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

No annotations are provided, and the description offers no behavioral details. It does not disclose whether the scale applies to a selected clip, if the operation is undoable, or any side effects. The unannotated description carries full responsibility and fails to disclose anything.

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 a single short phrase with no redundant words, making it highly concise. It is appropriately sized for the minimal information it contains, though the lack of structure is a minor issue.

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 minimal schema, no annotations, no output schema, and several similarly named sibling tools, the description is far from complete. It does not clarify the operation's scope, parameterization, or how to choose it over set_uniform_scale or set_scale_width_height, leaving an agent inadequately informed for reliable invocation.

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?

With zero parameters defined in the schema, there are no parameter semantics to explain. According to the rubric, a tool with 0 parameters receives a baseline of 4. However, the tool name implies a scale value is needed, which is a latent ambiguity not addressed by the description or schema.

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 uses the specific verb 'set' and resource 'clip scale', clearly indicating an action. However, it does not distinguish this tool from closely named siblings like set_uniform_scale or set_scale_width_height, so it lacks explicit differentiation.

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. The description provides no context about prerequisites, selection requirements, or situations where this tool is preferred.

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