map_zoom_to_layer

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

No annotations are provided, so the description carries the full burden. It states it zooms to the layer's full extent and returns the resulting canvas extent, but lacks detail on side effects or whether any map state changes are permanent.

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 concise sentences: the first states the action, the second adds a usage tip. No unnecessary words, front-loaded.

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 tool has one parameter and no annotations, but has an output schema. The description mentions the return value briefly. The simplicity of the tool means the description is nearly complete, though it could mention if the layer must be visible.

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 schema has 0% coverage for the single parameter 'layer_id', but the description adds meaning by stating it comes from project_list_layers, which is helpful context beyond the raw schema.

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 'Zoom the map canvas to a layer's full extent' with a specific verb and resource. It distinguishes from sibling zoom tools like map_zoom_to_selection and map_zoom_full.

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?

It provides a prerequisite: 'Use the id from project_list_layers.' This gives clear context on how to obtain the required parameter. While it doesn't explicitly exclude other scenarios, it implies when to use this tool.

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