map_zoom_to_extent

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

With no annotations, the description transparently discloses the core behavior: zooming to a bounding box and returning the resulting canvas extent. It also clarifies the effect of omitting crs. It does not mention any side effects or destructive actions, but none are expected for a zoom 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 just two sentences, front-loaded with the core purpose, and every word adds value. No extraneous text.

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?

The description covers the main inputs, output (resulting canvas extent), and a key behavioral detail (crs default). Given the many sibling zoom tools, it could mention when to prefer this over others, but it is otherwise complete for a simple zoom tool.

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%, but the description compensates by explaining the bbox array format (xmin, ymin, xmax, ymax) and the crs default behavior. This adds significant meaning beyond the bare schema types.

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?

Description clearly states 'Zoom the map canvas to a bounding box.' It specifies the action (zoom) and the resource (map canvas with bbox). This distinguishes it from sibling tools like map_zoom_to_layer or map_zoom_to_selection by focusing on an explicit bounding box.

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 explains how to use the tool: 'bbox is [xmin, ymin, xmax, ymax]' and crs defaults to canvas CRS, with instruction to pass crs when coordinates differ. However, it does not explicitly state when to choose this tool over alternatives like map_zoom_to_layer or map_pan_to, leaving some ambiguity for an AI agent.

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