Remove green colour cast from an image view by running SCNR with adjustable amount and protection method.
Run SCNR (Subtractive Chromatic Noise Reduction) to remove a green colour cast from a view.
| Name | Required | Description | Default |
|---|---|---|---|
| amount | No | Green removal amount, 0 to 1. | |
| view_id | Yes | PixInsight view identifier. | |
| protection | No | Protection method. | AverageNeutral |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the high-level purpose and does not say whether the tool mutates the view in place, requires an open view, or returns any result. This is a significant transparency gap for a process-runner tool.
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 a single, front-loaded sentence. It introduces the acronym expansion and states the tool's purpose without wasted words.
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 schema fully documents parameters above, making invocation feasible impossible, and the purpose is clear. However, the absence of annotations and an output schema means the description should provide more context about the operation's effect on the view and any prerequisites, so the definition is only minimally 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 100%, so the schema already documents all three parameters and their defaults. The description adds no parameter-level meaning beyond the schema, which meets the baseline but does not improve it.
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 uses a specific verb ('Run') and names the exact process (SCNR), plus its intended effect ('remove a green colour cast from a view'). It is clear, though it does not explicitly differentiate itself from sibling color-correction tools.
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 when to use the tool (when a green cast exists) but provides no explicit guidance about when to prefer it over alternatives like run_background_neutralization, restore_star_color, or run_curves. No exclusions or alternative routing is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.