photoshop_flatten_image

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 does disclose the end state (one background layer), but does not state that this is destructive/irreversible, whether hidden layers are included, or whether it depends on the document being in RGB/unsupported modes. Those gaps matter for a destructive document mutation.

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. It states exactly what happens and stops, which is the right size for a zero-parameter action.

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?

An output schema exists, so return values need not be explained, and there are no parameters to document. However, for a destructive, irreversible-sounding operation with no annotations, the description should minimally flag the destructive nature of the action, which it omits.

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?

Zero parameters, so the baseline is 4. The description adds nothing beyond the schema, but there is nothing to add, and the schema description coverage is 100%.

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?

Specific verb ('flatten') + resource ('all layers') with an explicit outcome ('into a single background layer'). An agent can distinguish this from the sibling photoshop_merge_visible_layers, which only merges visible layers rather than flattening all of them.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative photoshop_merge_visible_layers, which is the closest sibling and the key routing decision for an agent. Usage is only inferable from the verb.

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