ps_add_layer

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

No annotations are present, so the description must disclose side effects, but it only states the basic creation action. It does not mention where the layer is inserted, that it may become the active/selected layer, or any prerequisites/failure conditions beyond 'current document'.

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 one short sentence that front-loads the core action and target. The only extra phrase duplicates the optionality of the schema, but it is minimal and does not create bloat.

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?

This is a very simple one-parameter tool with no output schema, so the description is mostly adequate for invocation. However, because there are no annotations and no output schema, the description leaves open whether the call returns a layer reference and what positional side effects occur.

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 100%: the schema already documents name as an optional string. The description merely repeats 'name 可选' and adds no extra semantics such as naming rules, default naming behavior, or character limits.

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 uses a specific verb ('新建' / create) and a precise resource ('空白图层' / blank layer), anchored to '当前 Photoshop 文档' (current Photoshop document). The qualifier 'blank' distinguishes it from siblings such as ps_add_text_layer and ps_duplicate_layer even without naming 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?

There is no guidance on when to choose this tool over alternatives like ps_add_text_layer or ps_duplicate_layer. The only contextual cue is 'current document', which implies an open document prerequisite but does not state it.

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