Sdk Set Camera

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

Annotations already declare idempotent/non-destructive/non-read-only, so the safety profile is covered. The description adds genuinely non-obvious behavior: the write is a guarded compare-and-swap keyed on map/context/WKID, implying failure when preconditions don't match, and that coordinates are used as-is without guessing or projecting. It omits the confirm gate and animation behavior, keeping it short of a 5.

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 front-loaded sentence with no filler; the mechanism and the coordinate caveat are both delivered compactly. It borders on under-specification for a 13-parameter tool, but as raw structure it is efficient and 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?

An output schema exists so return values need not be explained, but with 13 parameters, 0% schema coverage, and no annotation-visible mutation nuance, the description leaves most invocation details (x/y/z/roll/pitch/heading/scale/confirm/duration semantics) unaddressed. An agent cannot reliably construct a call from this text alone.

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% across 13 parameters, so the description must compensate. It partially does: 'map/context/WKID' maps to the three required guard params (expected_map_uri, expected_context_generation, expected_spatial_reference_wkid), and '不投影坐标' hints at x/y semantics. But roll/pitch/heading/scale/z/confirm/duration_milliseconds receive no explanation at all.

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 states a specific verb and resource ('设置原生 MapView 相机' / set the native MapView camera) and discloses the operating mechanism (compare-and-swap on map/context/WKID). It distinguishes itself from the generic sibling arcgis_pro_set_active_view_camera only implicitly via 'native'/SDK framing and CAS semantics, so sibling differentiation is weak.

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 clause '不猜测或投影坐标' implies the caller must supply already-correct coordinates and that no projection is performed, which is a meaningful usage constraint. However, there is no explicit statement of when to prefer this tool over arcgis_pro_set_active_view_camera, arcgis_pro_map_camera, or arcgis_pro_set_map_default_camera, so usage is only implied.

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