zoom_to_selection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state what happens when nothing is selected (no-op vs. error), whether this mutates only the view, or whether it has any side effects like changing the active map.

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?

A single short sentence with no wasted words. However, the brevity edges into under-specification for a tool with a required parameter whose role is never mentioned.

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?

An output schema exists, so return values need no explanation, and the tool is simple with only two params. Still, the description omits the selection prerequisite and the required layer_name, leaving the agent to reconstruct usage from the schema alone.

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 100% and both parameters are documented in the schema (map_name defaults to active map; layer_name accepts a name from get_layers or a full dataset path). The description adds nothing beyond the schema and arguably creates confusion by omitting layer_name altogether.

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?

States a specific verb ('Zoom') and resource ('the map view'), scoped to 'currently selected features', which differentiates it from the sibling zoom_to_layer. It is clear what the tool does, though it never acknowledges the required layer_name parameter it actually takes.

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 versus zoom_to_layer, zoom_to_layer's share of scope, or the prerequisite that a selection must exist. The agent must infer that a selection must already be made before this tool is useful.

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