export_image

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

With no annotations, the description must carry the full behavioral burden, but it only states the core export action. It omits critical behavior such as whether existing files are overwritten, whether it modifies the source document, or how it handles output directories—details that the 'overwrite' parameter hints at but the description fails to address.

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, front-loaded sentence that efficiently communicates the primary function. It avoids unnecessary words and gets straight to the point, making it easy to parse quickly.

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, multiple sibling export tools, and no output schema or annotations, the description is too sparse to be considered complete. It lacks guidance on when to choose this tool, what the output looks like, and behavioral nuances, leaving a capable agent without enough context to invoke it correctly in all scenarios.

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 input schema documents all 7 parameters with descriptions, so the coverage is 100%. The description adds no extra meaning to any parameter, but since the schema is exhaustive, the baseline of 3 is appropriate; the description neither enhances nor contradicts the 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 ('Exports document pages') and specifies the output formats (JPG, PNG, TIFF), making the purpose unambiguous. It differentiates from the sibling 'export_pdf' by format, but it does not explicitly distinguish itself from other export-related siblings like 'batch_export' or 'quick_export'.

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 use this tool versus the other export tools in the sibling list. It does not mention any conditions, prerequisites, or alternatives, leaving the agent without context to choose the appropriate tool.

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