list_layers

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

Given the lack of annotations, the description must define the tool's behavior. It clearly defines the operation as a listing action and specifies the exact data points returned (layers and their specific status flags), which is highly transparent for a read 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 perfectly concise, using a single sentence to define the tool's purpose and data scope without any unnecessary language or filler.

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, zero-parameter read operation, the definition is highly complete. It specifies exactly what the tool does and what data is returned (layer status), allowing an agent to invoke it without needing further details.

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?

Since the tool requires zero parameters, the description does not need to add semantic meaning beyond the schema. The baseline score of 4 is applied here.

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 the specific verb 'List' and clearly identifies the resource 'drawing layers.' Furthermore, it specifies the exact attributes included in the listing: 'off/frozen/locked state,' giving precise scope.

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?

While the function is very clear, the description does not provide explicit guidance on when to use this tool versus other similar sibling tools, such as those related to entity lists or active drawings. Usage is implied by the tool name and content.

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