Zoom to Layer

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

The annotation idempotentHint: true indicates safe repetition. The description adds that it zooms to full extent, implying a read-like operation without side effects. No contradiction.

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?

One sentence, front-loaded with verb and resource, no redundant words.

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 tool's simplicity, the description covers the core behavior. Missing details like error handling (layer not found) or exact behavior, but still adequate.

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% and the description does not explain what layer_id refers to (e.g., name, ID). For a simple tool this is a gap, but the single parameter is self-explanatory given the context.

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 resource (map canvas), and the target (full extent of specified layer). It distinguishes well from siblings like set_canvas_extent or get_layer_extent.

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 explicit guidance on when to use this tool versus alternatives like set_canvas_extent or set_canvas_scale. The purpose is clear, but an agent could benefit from context on typical use cases.

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