flatten_sprite

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the mutation/safety profile is covered structurally. The description adds the useful '(in place)' detail meaning it overwrites the existing sprite rather than producing a new file, but it does not say what is lost (layer structure, groups, blend semantics) or whether the operation is undoable.

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 short sentence with the core action front-loaded and no filler. Nothing could be removed without losing meaning.

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 destructive, no-output-schema mutation the description covers the basic effect and the in-place nature, and annotations carry the destructiveness flag. It remains thin on what the destination layer is, how groups/background layers are handled, and how the filename argument should be supplied.

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?

There is one parameter, filename, with 0% schema description coverage, and the description never mentions it. With coverage this low the description is expected to compensate, but it does not say whether filename is a path, a sprite name, or whether it must reference an already-open document.

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 (flatten) and resource (all layers) plus the scope (in place), which is clearly distinct from a partial merge. It does not, however, name or contrast with the closest sibling, merge_layer_down, so the agent must infer the difference.

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?

There is no statement of when to use this versus merge_layer_down, convert_layer_to_background, or other layer-collapsing siblings, and no prerequisites are given. Usage is only implied by the tool name.

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