export_mxd_with_overlay_png

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose that the MXD is never saved, which is a key behavioral guarantee, and that confirm=true is required. However, it does not mention potential side effects (e.g., temporary files), what happens if confirm is false, or any other operational details. This is moderate disclosure but leaves gaps.

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 a single, concise sentence that front-loads the core purpose and then adds the critical constraint about confirm=true. There is zero waste, and the key information is presented immediately.

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 has 7 parameters, no annotations, no schema descriptions, and an output schema that is not detailed in the context, the description is far too minimal. It does not explain parameter usage, return value expectations, or edge cases. An agent would struggle to use this tool correctly with only the provided description and bare parameter 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?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It only mentions 'semi-transparent overlay' and 'confirm=true' but does not describe mxd_path, overlay_dataset, output_png, resolution, transparency, or overwrite. The meaning of these parameters is entirely left to the schema names, which are insufficient for an agent to call correctly. The description fails to add any meaningful parameter semantics.

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 a specific verb-resource pair: export an MXD preview with a temporary semi-transparent overlay. It also distinguishes itself from sibling tools like export_mxd_to_png and export_mxd_to_pdf by emphasizing the overlay and the fact that the MXD is never saved. This makes the tool's purpose unambiguous.

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 a prerequisite ('Requires confirm=true') but does not explicitly state when to use this tool versus alternatives. It implies a use case (preview with overlay) but lacks explicit guidance such as 'use this when you need an overlay' or 'use export_mxd_to_png for plain exports.' The confirm requirement is helpful but not a full usage guideline.

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