gimp_rotate_flip_image

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

Annotations already declare a mutating (readOnlyHint=false) but non-destructive operation, and the description usefully adds that the whole image is affected and that rotation is clockwise, which the enum alone does not convey. It does not disclose undoability, what happens when image_id is omitted, or interaction between simultaneous rotate+flip.

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 front-loaded sentence with no filler; the operation and its key qualifier (clockwise, entire image) come first. It is very terse, but nothing in it is wasted.

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 3-parameter tool with no output schema, the description covers the core behavior and rotation direction but leaves image_id semantics (which image is targeted when null) and flip-axis meaning undocumented in both schema and description.

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%, so the description carries the burden. It partly compensates by clarifying the clockwise rotation sense and the allowed angles, but 'voltear' never explains horizontal vs vertical flip and image_id is not mentioned at all.

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 pair (rotate/flip) and resource (the entire image), plus the allowed angles and clockwise direction. 'Imagen entera' implicitly separates it from layer-level siblings like gimp_transform_layer, but no sibling is named explicitly.

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?

Usage is only implied: 'entera' signals whole-image scope, which hints at when to prefer this over gimp_transform_layer, but there is no explicit when/when-not guidance, no mention of combining rotate and flip in one call, and no prerequisites.

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