rotate_image

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

With no annotations, the description carries the full behavioral burden. It does disclose one genuinely useful non-obvious trait, "the canvas grows to fit," telling the agent the result bounding box expands rather than clipping. It omits other important behavior: whether negative degrees rotate counterclockwise, whether the operation is destructive to existing pixels, how new corner regions are filled, and interpolation/quality characteristics.

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?

A single compact sentence with the core action front-loaded and the secondary behavioral fact (canvas growth) attached after a semicolon. Nothing is wasted, though the brevity is part of why parameter direction conventions go unstated.

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 one-parameter geometry tool with no annotations and no output schema, the description covers what it does and the main non-obvious side effect. The remaining gaps (sign convention, new-area fill, quality) are minor relative to the tool's simplicity, so it is close to complete.

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 0% and the single parameter "degrees" has no description in the schema, so the description must compensate. It adds the useful notion that measurements are clockwise and unbounded ("any angle"), but never states the sign convention for counterclockwise rotation or whether values wrap at 360. That leaves a real gap for the one required argument.

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?

"Rotate the whole image clockwise by any angle" gives a specific verb and resource, and "whole image" distinguishes it from layer-scoped siblings like transform_layer. It is not differentiated from the other geometry tools (flip, scale_image, resize_canvas), but an agent can still identify the operation unambiguously.

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 explicit when-to-use or when-not-to-use statement and no sibling is named as an alternative, so an agent must infer that this is the tool for arbitrary-angle rotation versus flip or scale_image. The clockwiseness plus "any angle" implies the use case well enough for a simple geometry operation, but guidance is only implied.

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