apply_image_transform

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds one behavioral trait (rotation is image-only, not node rotation), but fails to mention whether the transform overwrites existing transforms, what happens if the node has no image, or if the operation is reversible. No mention of side effects or auth requirements.

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 extremely concise: two sentences, no wasted words. It front-loads the overall purpose and immediately clarifies a critical behavioral nuance. Every sentence earns its place.

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?

Despite having 6 parameters and lacking an output schema, the description does not explain the return value (if any) or side effects. It does not mention whether the tool modifies the node in place, what the success/failure indicators are, or prerequisites like the node needing to have an image. For a transformation tool, this is incomplete.

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?

All six parameters have descriptions in the schema (100% coverage), so the description adds minimal extra meaning. It reinforces that rotation applies to the image inside the node, which is already in the schema but beneficial to restate. Baseline 3 is appropriate; the description does not compensate for any parameter gaps.

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 it adjusts image position, scale, and rotation within a node, and importantly clarifies that rotation applies to the image inside the node, not the node itself. This distinguishes it from sibling tools like rotate_node. However, it could be more specific about what 'within node' means (e.g., nodes with image fills) and how it differs from set_image or set_image_fill.

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 does not provide any guidance on when to use this tool versus alternative sibling tools such as set_image, resize_node, or rotate_node. It only distinguishes the rotation behavior. No when-to-use, when-not-to-use, or prerequisite conditions are mentioned, making it hard for an agent to decide contextually.

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