Create Layer

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

Disclosures beyond annotations: making the layer active and its effect on new artwork. Annotations already indicate it's a write operation (readOnlyHint=false) and not destructive. No mention of potential side effects like layer ordering or behavior with duplicate names.

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 concise sentences plus a terse arg list. Front-loaded with the core action. Every sentence adds value with no redundancy.

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 simple one-parameter tool with no output schema, the description covers purpose and basic behavior. Minor gap: no mention of behavior with no active document, but context signals already indicate this is likely handled externally.

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 coverage is 100%, with the description only restating the parameter name. No additional semantics beyond what the schema provides (minLength, required). Baseline score of 3 applies.

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 specifies the verb 'create' and resource 'layer in the active document', and clarifies that it makes the layer active. This distinguishes it from siblings like illustrator_set_active_layer which only switches active layer.

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 on when to use this tool versus alternatives such as illustrator_set_active_layer. Does not mention prerequisites (e.g., an active document must exist) or scenarios where another tool would be more appropriate.

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