Rotate / flip image

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

The annotations declare readOnlyHint=true, but the description describes writing an output file: 'Where to write the result' and naming it '<name>-rotated.<ext>'. That is a filesystem mutation and contradicts the read-only annotation, so the score is 1 despite otherwise detailed behavioral context about canvas growth, flip order, and EXIF handling.

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 one front-loaded paragraph with no repetition and is appropriately dense for a 10-parameter image tool. The website link is marginal for an agent, but the rest is efficient and well ordered.

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?

It covers operation semantics, ordering of EXIF/flip/rotate, output formats, output naming, and background behavior. With no output schema, it still leaves the exact return object structure unstated, but for a file-producing image tool it is mostly 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 description coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema: the flip applies after rotation as seen on screen, EXIF orientation is applied first, non-right-angle rotations grow the canvas, and uncovered corners use the background fill. It does not discuss quality or returnBase64, but the schema already covers those.

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 states a specific verb and resource: rotate and/or flip an image. It also captures the full operation scope, including arbitrary angles, horizontal/vertical flips, EXIF orientation handling, and output formats, so an agent can distinguish it from image_resize, image_crop, and pdf_rotate.

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?

It gives clear usage context, including that angle 0 fixes sideways phone photos via EXIF auto-orientation, that flips apply after rotation, and that 'keep' preserves the input format. It does not explicitly say when not to use this tool or name a sibling alternative, so it falls short of a 5.

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