photoshop_desaturate

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

No annotations are provided, so the description carries the burden; it states the mutation ('desaturate layer') but says nothing about reversibility, whether it is destructive, or which layer is affected if none is active. Has an output schema so return values need not be explained.

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?

A single front-loaded sentence with no wasted words; it says exactly what the tool does in the minimum space.

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 zero-param mutation with no annotations and an existing output schema, the description is adequate but thin: it omits whether the operation is destructive, requires an active layer selection, or can be undone, which an agent might need to know.

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?

Tool takes zero parameters, so there are no parameter semantics to explain; baseline 4 applies.

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 (desaturate) and resource (active layer) plus the resulting effect (black and white). An agent can distinguish it from siblings like photoshop_invert or photoshop_adjust_hue_saturation.

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?

Implies usage by naming the target as the 'active layer', which implies the layer must be selected first, but gives no explicit when-to-use or when-not-to-use guidance or alternatives (e.g., vs. hue/saturation adjustment).

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