listLayers

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

The annotations clearly state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which already set the safety profile. The description adds the return shape but not much behavioral context beyond that. It does not contradict annotations. Since annotations already cover the key behavior, the description adds minor context (return type) but not significant extra disclosure.

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?

One sentence describing purpose, one sentence for return value. No fluff. Front-loaded with the action.

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?

With output schema present and annotations covering safety, the description is sufficient for a simple read-only list operation. It tells the agent what happens (lists layers) and the return format. It could specify that the layers are objects vs strings, but that's a minor gap. The tool is simple, so completeness is adequate.

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 only one optional【来源：春色 inspiration cove words (cir(es); (2) (3) (4) (5) (6 (7) null (8 (9) null (10 null ) (11 null] (12_____ MCP uses schema descriptions. The description mentions the return type and that sessionId is used for multi-b} (20 null (21 null (22 null (23 null (26 null (27 null (" (28 null (31 null (

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 the purpose: 'List all layers currently managed by the page.' The verb 'List' is specific and distinguishes the tool from siblings like addGeoJsonLayer and removeLayer.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this is a read-only operation or when it should be preferred over queryEntities or getLayerSchema. The context of 'currently managed by the page' is some guidance but not explicit.

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