set_map_extent_from_layer

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool changes the map frame camera and optionally saves the project. However, it does not discuss permissions, reversibility, or failure scenarios, leaving gaps.

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 three sentences, each serving a distinct purpose: action statement, usage guidance, and behavioral effect. It is compact and front-loaded with the essential information, with no superfluous content.

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 five parameters and the presence of an output schema, the description covers the core purpose and typical use case. It could mention prerequisites or error conditions, but it is sufficient for most scenarios.

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 input schema already provides detailed descriptions for all parameters, including defaults and constraints. The description adds a brief mention of the save parameter and the internal functions used, but this does not significantly enhance understanding beyond the 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 the tool sets a layout map frame extent to match a named layer, using specific functions. It distinguishes from siblings like set_map_scale or zoom_to_layer by focusing on layer-based extent. The context of use before export is explicit.

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 advises using this before exporting a layout to focus on a dataset or area, providing clear context. It does not explicitly list when not to use it or name alternatives, but the intended use case is well stated.

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