gimp_gradient

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

Annotations declare a non-readonly, non-destructive write operation, but the description does not clarify which image layer is affected, whether it operates on the active layer, or any side effects. It only explains color defaults, leaving key behavioral context unstated.

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?

Two succinct sentences with the core action front-loaded and default behavior explained efficiently. No wasted words, though it could better structure the parameter hints.

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 schema descriptions and an output schema, the description is too thin. It omits target image/layer context, shape options, reverse flag, and any indication of where the gradient is applied.

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% for 11 parameters. The description mentions x1, y1, x2, y2, start_color, end_color, and gradient, but omits shape, reverse, image_id, and layer_id entirely, so it fails to compensate for the schema's lack of descriptions.

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?

States a specific verb ('Rellena') and resource ('degradado') with coordinate endpoints, clearly distinguishing it from a solid fill. Does not name the sibling tool (e.g., gimp_fill) it should be chosen over, but the gradient focus is evident.

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?

Describes default color behavior (start_color→end_color or foreground→background) and the 'gradient' parameter for named GIMP gradients. No explicit when-to-use vs. alternatives like gimp_fill; usage is implied by the gradient description.

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