Zoom to Layer

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

The annotation declares idempotentHint=true, meaning repeated calls have the same effect. The description adds no further behavioral context beyond this. Since the operation is simple and non-destructive, the description is adequate but not enhanced.

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, front-loaded sentence that conveys the core action efficiently. There is no redundant or extraneous information.

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 low complexity (1 parameter, no output schema), the description is minimal but insufficient. It lacks information about parameter format, what happens if the layer doesn't exist, or whether the zoom respects current scale constraints. The annotation helps but the description itself is incomplete.

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?

The description mentions 'specified layer' but does not clarify the meaning of 'layer_id' beyond the schema's title. Schema description coverage is 0%, so the description should compensate by explaining how to obtain or format the layer identifier. It adds almost no value.

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 action ('Zoom the map canvas') and the target resource ('to the full extent of the specified layer'). It distinguishes this tool from siblings like 'set_canvas_extent' (which sets to arbitrary coordinates) and 'get_layer_extent' (which returns the extent without zooming).

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 implies usage when you want to zoom to a layer's extent, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., 'set_canvas_extent' for custom extents). No when-not-to-use or prerequisite conditions are mentioned.

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