Set Canvas Extent

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

The annotation idempotentHint:true indicates the tool is safe to call repeatedly. The description adds that coordinates must be in the specified CRS, but does not elaborate on side effects like map redrawing or reversal.

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?

Two short sentences with no fluff. Every word contributes to the core purpose.

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 is too brief for a tool that alters the map state. Missing details on effect on canvas (zoom/pan), whether it sets the visible extent or project extent, and return value. Given no output schema, more context is needed.

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?

With 0% schema description coverage, the description only mentions the CRS parameter. The four coordinate parameters (xmin, ymin, xmax, ymax) are unexplained, leaving their meaning, order, and format ambiguous.

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 tool sets the map canvas extent. It distinguishes from siblings like get_canvas_extent (retrieval) and set_canvas_scale (zoom level), but could be more explicit about the effect (e.g., zooming the map).

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 like get_canvas_extent or set_canvas_scale. The description does not indicate prerequisites or typical use cases.

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