Set Active View Camera

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the operation is scoped to the CURRENT map view and validates the active map URI, which explains a behavioral prerequisite, but does not disclose what happens on URI mismatch or whether an active view is required.

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?

A single compact sentence that front-loads the action and lists the affected fields. Minimal waste, though the list of fields consumes space that could have been used for the more critical required-parameter explanation.

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 explained, and annotations cover the safety profile. However, for a 9-parameter mutation tool with 0% schema description coverage and multiple camera-related siblings, the description omits parameter formats, the role of the required params, and sibling differentiation.

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 must carry parameter meaning. It names the camera fields but provides no units (degrees vs radians), value ranges, coordinate system, or the meaning of the two required parameters (aprx_path, expected_map_uri), leaving all 9 parameters effectively undocumented.

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 (设置/set) and resource (相机/camera with X/Y/Z/scale/heading/pitch/roll) within the CURRENT map view. However, it does not differentiate from the very similar siblings arcgis_pro_sdk_set_camera, arcgis_pro_set_map_default_camera, or arcgis_pro_map_camera, leaving ambiguity about which camera tool to pick.

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?

Provides no guidance on when to use this tool versus arcgis_pro_sdk_set_camera or arcgis_pro_set_map_default_camera, both of which also set camera state. The mention of validating the active map URI implies a prerequisite (that a map view must be active) but does not state it explicitly.

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