zoom_to_layer

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

The description discloses the core behavior (zooms to layer extent) but omits details like what happens if the layer is empty or invisible, or whether the map view is modified permanently. No annotations are present, so the description carries the full burden, and it is minimally adequate.

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 succinct sentence with no superfluous words. It is well front-loaded and easy to parse.

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 presence of an output schema (though not visible here), the description does not mention return values. For a simple zoom action, it covers the essential purpose but lacks context on error handling or conditions.

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%, meaning the schema properties lack descriptions. The tool description does not explain the meaning or usage of 'map_name' or 'layer_name' parameters, leaving the agent to infer from names alone.

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 'Zoom the map view to a layer's extent' clearly states the action (zoom) and the target (layer's extent). It distinguishes the tool from siblings like add_layer or remove_layer, which involve different operations.

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 (e.g., zooming to a different object) or when not to use it. There is no mention of prerequisites or context.

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