adjust_color_balance

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

No annotations are supplied, so the description carries the full behavioral burden. It does add one useful fact ('Returns status dict') and notes that layer_name defaults to the active layer, but it never says whether the edit is destructive or undoable, what happens when the named layer or image index does not exist, or what keys the returned status dict contains.

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 purpose sentence is front-loaded and the parameter block is scannable, with no filler prose. It does repeat defaults and value types that also appear in the schema, but that repetition is justified at 0% schema description coverage.

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 six-parameter mutation tool with no annotations and no output schema, the description is adequate on inputs but thin on outcomes: 'Returns status dict' does not tell the agent what success or failure looks like, and nothing addresses permission, error, or undo behavior. It is minimum viable rather than complete.

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 supply all parameter meaning, and it does: it documents the three color axes with their -100 to +100 range and channel polarity, the three accepted 'range' values with their default, the image_index default, and the layer_name default-to-active-layer behavior. The only gap is that it does not clarify the interaction between image_index and layer_name or the allowed bounds of image_index.

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 and resource ('Adjust color balance ... of a layer') and names the tonal ranges it operates on, which tells an agent this is a tonal correction tool. It does not explicitly distinguish itself from sibling tonal tools like adjust_curves, adjust_brightness_contrast, or adjust_hue_saturation, so the agent must infer the difference.

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 never says when to reach for color balance versus the many sibling adjustment tools, nor does it state prerequisites such as an open image or an existing layer. Usage is only implied by the purpose sentence.

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