background_neutralize

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. The description adds the 'Checkpoints first' warning, which is valuable behavioral context for a destructive operation. However, it doesn't disclose what exactly gets modified (e.g., does it replace the image's background model, alter pixel values irreversibly?) or whether it requires a specific image state. The description adds some value beyond annotations but not rich behavioral detail.

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 extremely concise: one sentence with a parenthetical clarification and a two-word usage warning. Every word earns its place, and the key information (what it does, when it applies) is front-loaded. The 'Checkpoints first' warning is a critical addition that justifies its placement.

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 destructive linear-stage tool with 5 parameters and no output schema, the description is somewhat thin. It tells the agent what the tool does and that checkpoints are needed, but it doesn't explain the parameter semantics (especially reference_id and background_high), what the expected input image state is, or what the result looks like. The sibling list includes gradient_correction and color_calibrate, which are related but the description doesn't disambiguate. It's adequate but has clear gaps.

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 40%, meaning the schema documents some parameters (id, params, checkpoint, reference_id, background_high) but the description itself adds no parameter-level meaning beyond the schema. The description's 'equalize channel backgrounds' hints at what background_high might control, but it doesn't explain the relationship. With 40% coverage, the description partially compensates but doesn't fully bridge the gap for undocumented parameters like reference_id and background_high.

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: 'BackgroundNeutralization (equalize channel backgrounds) — linear stage.' This clearly identifies the tool as applying PixInsight's BackgroundNeutralization process to equalize channel backgrounds, and the 'linear stage' qualifier distinguishes it from tools used later in the processing pipeline. It doesn't explicitly name a sibling alternative, but the parenthetical and stage qualifier provide enough differentiation.

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 a clear context signal: 'linear stage' implies this should be used during the linear phase of processing, and 'Checkpoints first' gives a usage prerequisite. However, it doesn't explicitly state when not to use it or name alternative tools (e.g., gradient_correction, color_calibrate) that might be confused with it. The guidance is implied rather than explicit.

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