gimp_apply_filter

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

Without annotations, the description carries the burden of behavioral disclosure. It does disclose an important behavioral distinction: merge is destructive ('bakes it in') while append is non-destructive. It does not mention broader side effects, whether the layer is modified in place, or what happens with opacity/blend_mode, so transparency is partial.

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 concise sentences, front-loads the core purpose, and uses the second sentence to convey the key mode distinction. There is no filler or redundant restatement of the schema.

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?

Given seven parameters, two required, no annotations, and zero schema description coverage, the description is too thin for reliable invocation. It clarifies mode but leaves the agent guessing about how to construct GEGL operation parameters, how opacity and blend_mode interact, and what output to expect beyond the presence of an output schema.

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%, so the description must compensate for the schema's silence. It explains 'mode' well but leaves six other parameters unaddressed, including the critical 'op', 'params', 'layer_id', 'opacity', and 'blend_mode'. This is insufficient for a seven-parameter tool.

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 clearly states the action ('Apply a GEGL operation to a layer') and adds meaningful mode semantics: merge bakes it in, append adds a non-destructive effect. It is specific and readable, though it does not explicitly contrast itself with sibling tools like gimp_layer_effect or gimp_layer_effects.

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 gives useful context for choosing between the two modes, which helps usage. However, it offers no guidance on when to prefer this tool over sibling GIMP tools or when not to use it, leaving tool selection somewhat implied.

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