merge_layer_down

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

With no annotations provided, the description must carry the full behavioral burden. It discloses the basic action and direction but does not state that merging is destructive, that the upper layer is typically removed, or what happens to layer order, cels, or frames. The agent cannot anticipate the side effects of this 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?

The description is a single, tight sentence with no filler and the action is front-loaded. It is appropriately concise for a simple operation, even though the brevity contributes to gaps in other dimensions.

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 mutating tool with no annotations and no output schema, the one-line description is incomplete. It does not mention prerequisites such as requiring a layer below the target, irreversibility, or the resulting layer state, so an agent cannot fully predict the outcome of invoking it.

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?

Schema description coverage is 0% and the parameters `filename` and `layer_name` have no descriptions. The description does not clarify which layer is the source, which is the destination, or what `filename` refers to, so it fails to compensate for the missing schema guidance.

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 ('merge') and the specific target ('the layer below it'), making the operation concrete. It is distinguishable from related sibling tools like flatten_sprite, reorder_layer, or delete_layer, though it does not explicitly call those distinctions out.

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?

The description defines the operation but provides no guidance on when to prefer it over related tools such as flatten_sprite or delete_layer. There are no preconditions, exclusions, or alternative conditions mentioned, leaving the agent to infer usage entirely from the tool name.

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