Export Layout Image

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds that write/path restrictions are bound by service capabilities, which is a useful if vague behavioral note, but it does not explain overwrite behavior, output location rules, or permissions.

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?

It is short and front-loads the purpose, but the second clause is generic boilerplate ('returns verifiable structured results; write and path restrictions are subject to service capabilities') that adds little substance while offering no actionable size.

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 an 8-parameter file-writing tool with 0% schema coverage, the description is too thin: it never names required inputs, image formats, DPI/quality defaults, or overwrite behavior. The existence of an output schema excuses explaining return values, but a great deal that the agent needs is missing.

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 8 parameters (aprx_path, layout_name, output_path, image_format, jpeg_quality, resolution_dpi, transparent_background, world_file), and the description explains none of them. The only hint, 'path restrictions,' is too vague to compensate for the 0% coverage 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?

The description says 'ArcGIS Pro：导出布局' (export layout), a verb+resource, but it essentially restates the title minus 'image' and does not differentiate from the sibling arcgis_pro_export_layout_pdf. An agent can tell it exports a layout but not why it should pick this over the PDF/map-image exporters.

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 when-to-use guidance and no mention of the many alternatives (export_layout_pdf, export_map_to_image, export_active_view_image). The trailing clause about write/path limits is a constraint, not usage selection guidance.

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