gimp_new_image

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose key behavior: the image is RGB, has exactly one layer, and accepts specific fill values. However, it does not mention side effects, color-string formats, prerequisites like a running GIMP instance, or failure behavior.

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 two short sentences with the main action front-loaded and the fill options presented as a compact list. Every word adds value and there is no redundant or vague filler.

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?

The tool is simple and the output schema plus parameter defaults cover some gaps, but with no annotations the description still lacks operational context such as prerequisites, color parsing, and call-time side effects. It is adequate for straightforward invocation, but not fully complete for an agent unfamiliar with the GIMP environment.

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?

The description adds meaningful detail for the fill parameter by enumerating valid values ('transparent', 'white', 'black', 'foreground', 'background' or any colour), which the schema leaves undocumented. It does not explain width and height units, but their roles are fairly obvious from the parameter names and default values in the schema.

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: 'Create an RGB image with one layer', so an agent immediately knows the tool's core function. It does not explicitly contrast with siblings like gimp_open or gimp_list_images, but the creation semantics are clear enough to avoid confusion.

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 implies this tool is for creating a new blank RGB image, but it provides no explicit when-to-use guidance or alternatives. It does not mention that gimp_open would be used for existing images or gimp_list_images for discovering current images.

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