Map Camera

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured fields. The description's added sentence ("returns verifiable structured results; write and path restrictions follow service capabilities") is generic boilerplate that says nothing specific about this tool's behavior, and the mention of write restrictions is mildly confusing on a read-only tool.

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 text is short, but brevity here comes from omission rather than efficiency; the second sentence is template filler that could apply to any tool. Nothing is front-loaded with actionable meaning.

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 no explanation, but the core question — what this tool actually does to the camera — remains unanswered, and both required parameters are opaque. For a tool with a dedicated output schema and two required inputs, this is insufficient.

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 supplies no information about aprx_path or map_name at all — no format, no expectations about what an aprx path or map name should reference. With two required, fully undocumented parameters, the description fails to compensate for the schema gap.

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?

"ArcGIS Pro：camera地图" essentially restates the tool name and title (Map Camera) without stating a verb or what operation is actually performed on the camera. It does not distinguish this tool from the many camera/view siblings such as arcgis_pro_sdk_set_camera, arcgis_pro_set_active_view_camera, arcgis_pro_set_map_default_camera, or arcgis_pro_map_pan_to_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?

There is no statement of when to use this tool versus alternatives, and no prerequisites or context. With several near-identical camera siblings in the toolset, the absence of any routing guidance leaves the agent to guess, which is exactly the situation usage guidance exists to resolve.

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