set_transform

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

No annotations are provided, so the description carries the full burden, and it does disclose real behavior: rotation is in clockwise degrees, width/height maintain proportions, and crop is measured in SOURCE pixels with [] clearing it. It says nothing about permissions, reversibility (undo), or what happens when crop is applied to a non-image layer, so for a mutation tool the disclosure is partial.

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?

Three dense, front-loaded sentences with zero filler; the core transformation verbs come first and parameter notes follow compactly. Every clause carries semantic information.

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 an 11-parameter mutation tool with no annotations and no output schema, the description covers the non-obvious parameters well but omits x/y/scale/flip semantics and the project parameter, and gives no note on irreversibility. Adequate but with clear gaps given the complexity.

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 description coverage is 0% across 11 parameters, so the description must compensate; it partially does by explaining width/height semantics, crop's [x,y,w,h] format and source-pixel coordinate space, and rotation's units/direction. x, y, scale, flip_h, flip_v, and project remain undocumented, leaving roughly half the surface unexplained.

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 names specific verbs (move/scale/rotate/flip) and the resource (a layer), so the agent knows exactly what operation class this is. It does not, however, differentiate itself from overlapping siblings like move_layer, align_layer, or resize_image, so the agent must infer which of these to pick.

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 when-to-use / when-not-to-use guidance and no mention of the sibling alternatives (move_layer, align_layer, resize_image, crop_canvas) that overlap heavily with this tool. The agent gets no routing help at all.

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