export_map_view

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

With no annotations, the description carries the full burden. It usefully discloses the environmental precondition (the map tab must be open) and the return format (an inline image), which goes beyond the schema. It does not state error behavior when the tab is closed, whether a file is written when output_path is supplied, or any side effects/reversibility, so the behavioral picture is partial.

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?

Two short sentences, zero filler, and the core action is front-loaded before the prerequisite. Every clause earns its place by adding either purpose or a constraint.

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?

For a 7-parameter tool with 100% schema coverage, no annotations, and no output schema, the description covers the essentials: what it renders, what it returns, and the environment requirement. It stops short of describing failure modes or how file output interacts with return_image, which would be the remaining gap.

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 100%, so dpi, width, height, map_name, output_path, return_image, and zoom_to_layer are already documented in the schema. The description adds no syntax, format, or interaction detail (e.g., how zoom_to_layer interacts with width/height) beyond that, so the baseline of 3 applies.

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 precise verb+resource: 'Render the map view to PNG and return the image,' which is unambiguous about the output artifact. It also frames intent ('the way to visually check a map'), implicitly separating it from coordinate-returning siblings like get_map_view. However, it never names a sibling explicitly, so an agent must infer the boundary from intent alone.

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 clear context for use ('the way to visually check a map') plus a hard prerequisite ('Requires the map's tab to be open in ArcGIS Pro'). There is no explicit when-not guidance or named alternative such as export_layout or export_map_series, so routing among export siblings is left to inference.

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