List Layers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that the tool enumerates all LayerObjects and describes the per-entry return contents: name, optional color, and flag dict. It stops short of explicitly stating that it has no side effects or how it behaves with no active document, but the term 'Enumerate' strongly implies a read-only operation.

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, well-structured sentence. It front-loads the primary purpose and follows with the relevant return details. Every phrase contributes information, and there is no filler or repetition.

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 zero-parameter list tool with no output schema, the description is complete: it names the resource scope, the enumeration behavior, and the exact fields returned per layer. An agent has enough information to invoke the tool and interpret its result without further clarification.

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?

The input schema is empty with zero parameters, so the baseline is 4. No parameter-level description is needed because there is nothing for the agent to populate or disambiguate.

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 ('Enumerate') with a clear resource ('every LayerObject') and scope ('in the active document'). It clearly differentiates this listing tool from the layer-related siblings like create_layer, assign_to_layer, and set_layer_flags, since they are all about mutation or assignment rather than enumeration.

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 intended usage is implied: if an agent needs to inspect all layers in the active document, this is the tool. However, there is no explicit guidance about when not to use it or which alternative to choose, such as get_object_layer for a single layer or set_layer_flags for modifying flags.

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