export_mxd_to_png

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does mention the confirm requirement and the use of a scratch directory, which is useful, but it does not disclose whether the operation is destructive to the original MXD (though it says 'copy'), what happens with the 'overwrite' parameter, or any error/return behavior. The description is minimal and leaves significant behavioral aspects unspecified.

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 extremely concise with no filler words, which is positive, but it is under-specified to the point of being insufficient. The core action is front-loaded, but the lack of additional context makes it feel incomplete rather than efficiently concise. It earns a mid-score because it is not verbose, but it also does not fulfill the purpose of a helpful description.

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 (5 parameters, no schema descriptions, no annotations) and the presence of an output schema (which we cannot see), the description is grossly incomplete. It does not explain any parameters, potential side effects, return values, or usage context. An agent would struggle to call this tool correctly without external knowledge.

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 parameter meanings. However, the description does not mention any parameters other than confirm (and only as a requirement). It gives no insight into what mxd_path, output_png, overwrite, or resolution mean, leaving an agent to guess from names alone. This is a severe gap given the lack of schema descriptions.

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 action ('Export'), the resource ('an MXD copy'), and the output format ('to a PNG') as well as the destination ('in the configured scratch directory'). This distinguishes it from sibling tools like export_mxd_to_pdf (different format) and export_mxd_with_overlay_png (with overlay), so an agent can easily tell it apart.

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 no guidance on when to choose this tool over its siblings, such as export_mxd_with_overlay_png or export_mxd_to_pdf. It mentions a prerequisite ('Requires confirm=true') but does not explain the conditions under which this tool is appropriate or alternatives to consider. An agent would need to infer usage context from the schema or sibling names.

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