Get Layers

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

The description is consistent with annotations (readOnlyHint: true) and adds context about pagination and the response including total_count. It does not contradict annotations, and the behavioral traits are well-disclosed for 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 two sentences with no redundant information. It front-loads the main purpose and is structured for quick understanding.

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?

Given the low complexity, presence of output schema, and good annotations, the description is complete. It covers purpose, pagination, and response content (total_count) without missing essential context.

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 description explains the purpose of parameters ('Use limit/offset for pagination'), adding meaning beyond the schema which only provides defaults and types. With 0% schema description coverage, the description compensates well.

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 'List layers in the current project with IDs, names, types, visibility, and type-specific info.' It uses a specific verb (list) and resource (layers) and distinguishes from siblings like get_layer_tree by specifying a flat list with specific fields.

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 description mentions pagination ('Use limit/offset for pagination') but does not provide explicit guidance on when to use this tool over alternatives like get_layer_tree or get_active_layer. The usage is implied for a flat list with pagination.

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