desaturate

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

The description does not specify whether the operation is destructive or creates a new sprite, nor does it clarify that frame/layer parameters limit the effect. With no annotations, these behavioral traits remain hidden, risking misuse.

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?

Extremely concise single sentence that conveys the core function. However, given the number of parameters and complexity, the brevity comes at the cost of completeness.

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?

Lacks explanation of return value, side effects, or scope. With no output schema and high parameter count, the description is insufficient for an agent to use the tool correctly in diverse contexts.

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?

Only 'amount' is explained (percent, 0-100). The critical 'filename' parameter and optional 'frame'/'layer' are not described. Schema coverage is 0%, so the description should compensate but fails to clarify the meaning of three out of four parameters.

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 ('desaturate') and target ('toward grayscale') with the key parameter 'amount' and its range (0-100). It distinguishes this tool from siblings like 'adjust_hue_saturation' which handle broader color adjustments.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that this tool fully desaturates at 100% or that other tools might offer more nuanced color effects. The agent receives no decision support.

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