export_mxd_to_pdf

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

With no annotations, the description carries the full burden. It usefully discloses that the operation works on a copy (implying non-destructive behavior) and that the output is placed in the configured scratch directory. However, it does not clarify overwrite behavior, side effects, or what happens if the output already exists.

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 short sentences, no filler. The primary purpose is front-loaded, and the confirm requirement is the second most important fact for successful invocation. Every word contributes.

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 tool with five parameters, no annotations, and no output schema, the description should explain more. It captures the core action and confirm gate but omits meaningful behaviors such as overwriting existing PDFs, how resolution is interpreted, and any expected return value or status. The agent can call it correctly only if it guesses the parameter semantics from names.

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 schema provides no param descriptions, only names and defaults, so the description needs to compensate. It addresses the crucial confirm parameter ('Requires confirm=true') and the scratch-directory context, but it leaves mxd_path, output_pdf, overwrite, and resolution semantics mostly to be inferred from their names and types.

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 specific verb ('Export'), a specific resource ('an MXD copy'), and a concrete output ('a PDF in the configured scratch directory'). This clearly distinguishes it from sibling conversion tools like export_shp_to_pdf by emphasizing MXD and the scratch directory.

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 only usage-related guidance is 'Requires confirm=true', which is a precondition rather than a when-to-use instruction. It does not mention alternatives or explicitly state when this tool should be chosen over a sibling export tool.

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