Render an ArcGIS Pro layout to a temporary image for visual checking without writing a file, so you can validate it while building.
Render a layout to a temporary image and return it, without writing a file -- use it to visually check a layout while building it.
| Name | Required | Description | Default |
|---|---|---|---|
| dpi | No | Render resolution. | |
| layout_name | Yes | Layout name. |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden, and it does disclose the key behavioral trait: output is a temporary render and no file is written, which is the main side-effect an agent needs to know. It does not specify the returned image encoding (bytes, path, base64) or render cost/limits, leaving some behavioral detail unstated.
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 that leads with the action, then the distinguishing constraint, then the intended use. No filler or redundant restatement of the title.
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 simple two-parameter render tool with no output schema, the description covers purpose, side-effect profile, and usage context adequately. The remaining gap is the shape of the returned image, which an agent might need given the absence of an output schema.
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% and both parameters (layout_name, dpi) are documented in the schema. The description adds no parameter-level meaning 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?
Specific verb (render) plus resource (layout) and an explicit scope qualifier: 'to a temporary image ... without writing a file.' This clearly separates it from the sibling export_layout, which persists output, so an agent can pick correctly without opening either schema.
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?
States a clear use case: 'use it to visually check a layout while building it,' i.e. iterative preview during authoring. It does not name export_layout explicitly as the alternative for producing a file, so the when-not condition is only implied by the phrase 'without writing a file.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.