set_scale_width_height

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

Annotations already indicate this is a write operation (readOnlyHint=false). The description adds the behavioral condition about Uniform Scale but does not disclose any other side effects, such as overwriting existing values or interaction with keyframes. It provides modest transparency beyond annotations.

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, concise sentence that immediately states the action and the critical prerequisite. No filler or redundant information, making it highly efficient for an AI agent.

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 simple setter tool with no output schema, the description covers the essential context: what it does and when it can be used. It could mention return values or confirmation, but the condition is the most important contextual detail. The lack of output schema diminishes the need for extensive return documentation.

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?

Schema coverage is 100% with descriptions for each parameter (node_id, scale_width, scale_height). The description reinforces the purpose of the parameters (independent scale) but does not add additional meaning beyond what is already in the schema. Baseline 3 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 clearly states the action ('Set independent Scale Width and Scale Height'), identifies the resource ('on a clip'), and distinguishes itself from sibling tools like 'set_uniform_scale' by specifying the prerequisite that Uniform Scale must be OFF.

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?

The description includes a clear usage condition: 'requires Uniform Scale to be OFF.' This guides the agent to check or set that property beforehand. It does not explicitly list alternatives but the condition effectively differentiates when to use this tool versus others.

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