export_layout_pdf

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

No annotations are provided, so the description carries the full burden. It discloses that the tool reads the .aprx project (read-only), writes output inside PathGuard allowed roots, and requires overwrite=true for existing files. It does not mention any other side effects, which is acceptable for a standard export operation.

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 description is two sentences long, front-loading the core purpose and usage context. Every sentence adds value without verbosity, making it highly efficient for an AI agent to parse.

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?

Considering the tool has six parameters (nested under one) and no annotations, the description covers the essential purpose, usage, and key behavioral constraints (PathGuard, overwrite). With an output schema presumably present, return values need no elaboration. Minor gaps exist (e.g., not mentioning that layout_name can be null to use the first layout), but overall completeness is good.

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?

The input schema already provides detailed descriptions for all parameters (aprx_path, out_pdf, overwrite, resolution, layout_name, image_quality), covering 'schema_description_coverage' effectively. The description adds minimal extra value beyond stating the project is read and the output path constraints, so a baseline of 3 is appropriate.

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 clearly states the tool exports a selected ArcGIS Pro layout to PDF using layout.exportToPDF. It distinguishes this from sibling tools like export_layout_png (PNG) and export_map_as_image (image) by specifying the PDF output format.

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?

The description provides explicit usage context: 'print-ready map sheets, reports, submittals, or archival exports with controlled DPI and image quality.' It does not explicitly say when not to use or mention alternatives, but the context is clear enough for an AI agent to decide.

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