Export a page to a file

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

The readOnlyHint annotation indicates the document itself is not modified, and the description clarifies output is an image file. It does not detail side effects like file overwriting or error conditions, but the annotation covers the main safety concern.

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 compact and every sentence adds useful information. It front-loads the primary purpose and then provides parameter-specific details without unnecessary repetition.

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?

The purpose, parameters, and supported formats are all covered. Return value details are not specified, but the context indicates an output schema exists, so that omission is acceptable; however, no error or fallback behavior is mentioned.

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?

All four parameters are explained with meaningful semantics: path resolution, page selection via name/index, document selection, and max_pixels behavior for raster formats. This goes well beyond the bare schema.

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: writing a page to an image file on disk. It lists supported formats and distinguishes the tool from PDF export and page rendering siblings by focusing on image files.

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 explains how parameters behave but does not explicitly say when to prefer this tool over visio_export_pdf or visio_render_page. It lacks direct guidance on alternatives or use-case boundaries.

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