photoshop_merge_visible_layers

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

No annotations are provided, so the description carries the full behavioral burden. It omits that this is a destructive, structure-destroying operation on the layer stack, whether it can be undone, and what happens to hidden layers — significant gaps for a mutation tool with zero annotation coverage.

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 filler, which is appropriate for a no-argument tool. It is arguably too terse given the missing usage and destructive-behavior context, but there is no wasted text.

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 output schema exists, so return values need not be explained, and there are no parameters to document. Still, the description leaves the destructive nature and the visible-vs-all-layers distinction unstated, which is exactly the context an agent needs before collapsing a layer stack.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to clarify; the schema fully covers the (empty) input contract. No parameter-level value could be added.

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 ('merge all visible layers into one composite layer'), so the action is unambiguous. However, it does not differentiate itself from the closely related sibling photoshop_flatten_image, which an agent could easily confuse with this one.

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 versus alternatives — most notably photoshop_flatten_image, which also collapses layers. The description never explains the visible-only scoping constraint that is the whole point of choosing this tool over flatten.

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