set_scale_width_height

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

The description indicates the tool modifies clip properties (set Scale Width/Height) and includes a necessary condition, but does not disclose side effects, error behaviors, or permission requirements. With no annotations, the description carries the full burden, and this is adequate but not thorough.

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, front-loaded sentence that conveys the action, resource, and key condition without any redundant or unnecessary words.

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 tool's simplicity (3 required params, no output schema, no nested objects), the description covers the essential functionality and a critical prerequisite. It lacks mention of return values or error handling, but these are not critical for a property-setting tool.

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?

Input schema has 100% description coverage for all three parameters (node_id, scale_width, scale_height). The description adds no additional semantic value beyond stating 'independent' scaling and the prerequisite, so 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 tool sets independent Scale Width and Height on a clip, with a specific prerequisite (Uniform Scale must be OFF). This distinguishes it from siblings like set_clip_scale and set_uniform_scale, which handle uniform scaling.

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 explicitly states the prerequisite 'requires Uniform Scale to be OFF', guiding when to use this tool. However, it does not name alternative tools or provide explicit instructions on when not to use it.

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