Export a PDF

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

The readOnlyHint annotation indicates the tool does not mutate the document, and the description does not contradict that. However, the description does not mention side effects such as creating or overwriting a PDF file at the destination path.

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 short, direct, and well-organized. Every sentence and parameter line adds relevant information without unnecessary verbosity.

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 tool is fairly simple and the description covers the main inputs and behavior. It does not describe the return value, but an output schema is present, so omitting return-value details is acceptable.

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 description adds useful meaning to each parameter, such as 'Omit for the active document' and 'Export every page rather than a single one.' It lacks some detail, like whether page is a name, number, or 1-based index, but overall it substantially supplements 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 name and description clearly state the tool exports a document to PDF. However, it does not explicitly distinguish itself from the sibling visio_export_page, relying on the parameter hints to imply the document-level scope.

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 implies usage by mentioning paths and page options, but it does not explicitly state when to prefer this tool over visio_export_page or other export-related tools. Usage guidance is present only through the parameter descriptions.

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