export_page_as_image

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says the page is exported as an image; it does not mention whether an existing output file is overwritten, whether the document must be open, how DPI affects the result, or any side effects of writing to output_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 a single focused sentence and the format list is front-loaded in parentheses. It is appropriately terse, though it could spend one more sentence on usage or output behavior without becoming bloated.

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 file-exporting tool with five parameters and no annotations, this description is incomplete. It omits output-path semantics, format/dpi constraints, and any conditions needed for a successful export, so an agent cannot fully plan the call from the description alone.

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 should compensate by explaining the parameters, but it only lists image formats. It adds no meaning for doc_id, output_path, page_number, or dpi, leaving an agent to rely on parameter names alone.

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 uses a specific verb and resource: 'Export a page as an image file,' and it lists the supported formats (bmp, jpg, png). It is clear enough to identify the action, but it does not differentiate from the sibling 'save_as_image', so the purpose is not fully disambiguated.

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?

No guidance is given about when to choose this tool over alternatives such as 'save_as_image' or 'print_document'. There are no conditions, exclusions, or examples, so an agent must guess which export tool fits a given task.

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