Export Report Pdf

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so safety is largely covered. The description adds that results are 'verifiable structured results' and that write/path restrictions depend on service capabilities, which is useful but vague and not operationalized.

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 action, which is good. The second clause about verifiable results and capability-dependent restrictions is generic boilerplate that does not add actionable detail, so it does not fully earn its place.

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 mutation tool with three required, undocumented parameters, the description is too thin: it omits parameter meaning, prerequisites, and sibling routing. The existing output schema does relieve it of explaining return values, but that alone does not close the gap.

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 never mentions aprx_path, report_name, or output_pdf_path, so the agent gets no format, path-convention, or naming guidance for any of the three required parameters. The passing reference to 'path restrictions' is too generic to compensate.

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?

States a specific verb+resource (export report) that clearly identifies the action. However, it does not differentiate from close siblings like arcgis_pro_export_layout_pdf, arcgis_pro_export_map_series_pdf, or arcgis_pro_export_chart, so an agent must infer from the name which export target applies.

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 gives no when-to-use guidance, no prerequisites, and no named alternatives. It never explains when exporting a report is preferable to exporting a layout or map series, leaving the routing decision entirely to the tool name.

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