Set Layer Visibility

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

The description aligns with the idempotentHint annotation (calling repeatedly has same effect). However, it does not disclose what happens if the layer does not exist, whether changes are saved automatically, or any side effects. The description adds minimal value beyond the annotation.

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 very concise (one sentence, no filler). However, it is too brief to be fully helpful; it sacrifices substance for brevity. It could be expanded with minimal additional context.

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 an output schema present, the return value is presumably documented there, but the description lacks crucial input context. It does not cover error scenarios (e.g., invalid layer), the role of optional parameters, or scope of effect. Incomplete for a tool with 3 parameters.

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 description coverage is 0%. The description does not explain any of the three parameters: what 'layer' expects (name/ID?), the effect of 'visible' boolean, or when 'map_name' is needed. This is a major gap as the description fails to compensate for missing schema documentation.

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 'Show or hide a layer on the map' clearly states the action (toggle visibility) and the resource (a layer). It distinguishes from sibling tools like add_raster_layer and remove_layer which add/remove layers, and zoom_to_layer which navigates.

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 add_layer or remove_layer. No mention of prerequisites like the layer must exist or that map_name is needed for multi-map projects.

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