Sdk Zoom Layer

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

Annotations already disclose readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds a small behavioral detail (can zoom only the current selection and maintain view direction), but it omits important operational context such as the SDK session/lease requirements and failure behavior.

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 front-loaded sentence with no filler, and the core action and constraints are stated immediately. It is appropriately terse for a description, even if the surrounding definition is incomplete.

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?

An output schema exists, so return values need not be described. However, with 8 parameters, 4 required, and 0% schema description coverage, the one-sentence description leaves the agent without enough information to correctly supply session references, expected map/context identifiers, or confirmation behavior.

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%, so the description carries the full burden. It clarifies layer_uri, selected_only, and maintain_view_direction, but leaves the required sdk_session_ref, expected_map_uri, and expected_context_generation completely undocumented, along with confirm and duration_milliseconds.

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?

States a specific verb (zoom) and resource (native MapView by exact layer URI), which lets an agent distinguish it from generic zoom tools like arcgis_pro_zoom_to_layer. It does not explicitly name or route to a sibling, so it stops short of a 5.

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 when-to-use guidance, no prerequisites, and no alternatives are mentioned. The agent must infer from the name and context when this SDK-level zoom should be preferred over arcgis_pro_zoom_to_layer or arcgis_pro_zoom_active_view_to_layer.

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