Export Layout Pdf

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

Annotations already convey the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false). The description adds a small amount of behavioral context — that results are structured/verifiable and that path/write limits depend on service capability — but does not state overwrite behavior for an existing output_pdf_path, permissions, or runtime characteristics.

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?

Short and front-loaded, so it is not bloated. But the brevity comes at the cost of substance — the second clause is boilerplate that occupies space without informing an invocation.

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 described. Still, for a 4-parameter export tool with many near-identical siblings and 0% schema coverage, the description omits parameter meaning, differentiation, and output-path behavior, leaving significant gaps.

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 mentions none of the four parameters (aprx_path, layout_name, resolution_dpi, output_pdf_path). It does not compensate for the coverage gap, leaving required vs optional path formats and the DPI default unexplained beyond the schema's bare titles.

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 clear verb + resource ('导出布局' / export layout), which is understandable. However, it gives no differentiation from close siblings like arcgis_pro_export_layout_image, arcgis_pro_export_map_series_pdf, or arcgis_pro_export_report_pdf, so an agent cannot tell which export tool applies without reading schemas.

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 indication of when to use this tool versus alternatives or any prerequisite/workflow guidance. The only adjacent information is a generic note that write and path restrictions follow service capabilities, which is not usage guidance.

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