gimp_batch_recipe

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 the main side effect—writing outputs to output_dir—and the recipe interface requirement. However, it does not mention whether existing files are overwritten, whether output_dir is created, or how errors are handled.

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 sentences with no filler; the core batch behavior is front-loaded and the recipe contract is stated as a concise constraint. Every word earns its place.

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 the five-parameter schema and zero schema documentation, the description is too thin for correct invocation without additional inference. It omits how the recipe is named, what params should contain, how output_ext is used, and whether output_dir must pre-exist. An agent could call this confidently only for the simplest cases.

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, but it only explains two of five parameters (input_glob and output_dir). The meaning of name, params, and output_ext is left entirely to inference, and the relationship between params and the recipe invocation is not clarified.

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 action ('Run a recipe') and the exact batch scope ('every file matching input_glob') while also specifying the destination ('writing to output_dir'). This clearly differentiates it from siblings like gimp_run_recipe, which presumably handles a single recipe execution.

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 communicates a clear usage context: batch processing over files matched by a glob. It also provides an important recipe contract ('Recipes must accept input_path and output_path'), which helps an agent decide whether this tool is appropriate. It does not explicitly name alternatives or when-not-to-use conditions, so it stops 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.