Krita Create Layer

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

With no annotations, the description carries the full burden. It discloses the important side effect that the new layer becomes active and explains stacking via 'above'. However, it omits prerequisites (e.g., open document), valid layer-type values, and behavior when a layer name already exists, so disclosure is partial.

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?

Two short sentences with no filler. The core purpose is front-loaded, and the parameter note about 'above' earns its place because it clarifies a non-obvious default.

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?

Despite the presence of an output schema, this is a five-parameter tool with no annotations and incomplete parameter semantics. The description does not define valid type values, opacity/blending-mode behavior, or document prerequisites, leaving the agent to guess for non-default calls.

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 descriptions are absent for all five parameters, so the description must compensate. It explains only 'above' and vaguely hints that 'type' selects paint or group layers; the required 'name', 'opacity', and 'blending_mode' are left semantically unexplained.

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 operation ('Create'), the resource ('layer'), and the supported kinds ('paint or group layer'). It is not merely a restatement of the title, and the active-layer side effect adds useful scoping. It does not explicitly differentiate from sibling krita_duplicate_layer, but the action is unambiguous.

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 is given for when to choose this tool over alternatives such as krita_duplicate_layer or krita_set_active_layer. The only contextual note is about the 'above' parameter, which is parameter usage rather than tool selection guidance.

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