export_layout_pdf

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

No annotations provided; description discloses file access ('Reads .aprx project and writes out_pdf'), PathGuard constraints, and overwrite requirement. However, it does not mention mutation behavior, side effects, or permission requirements, which would be beneficial for a write 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?

Two sentences efficiently convey purpose, use cases, and key constraints. Well-structured and front-loaded with core action.

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?

Given the tool's complexity (6 parameters) and presence of an output schema, the description covers essential behavioral context (PathGuard, overwrite) and use cases. No major gaps remain.

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 descriptions for parameters are detailed and cover semantics well (e.g., resolution range, image quality enum). The description adds minimal value beyond schema, but baseline 3 is appropriate since schema does the heavy lifting and descriptions are comprehensive.

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?

Description uses specific verb 'export' and resource 'ArcGIS Pro layout to PDF file', clearly distinguishing from sibling tools like export_layout_png and export_map_as_image by mentioning 'print-ready map sheets, reports, submittals, or archival exports'.

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?

Description provides clear use cases ('print-ready map sheets, reports, submittals, or archival exports') but does not explicitly state when not to use this tool or name alternatives. The implied guidance is adequate given sibling context.

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