quick_export

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'exports' without mentioning whether files are overwritten, whether the operation opens dialogs, whether it requires a saved document, or what happens on failure. For a tool that writes an output file, this is a meaningful gap.

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 short sentence that gets to the point quickly. The word 'Quickly' adds a minor usability flavor but is somewhat redundant; overall the size is appropriate for the function.

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?

With no output schema and no annotations, the description should compensate by explaining format-specific behaviors, conditional parameters, and expected results. The current description is too sparse: it does not mention that pageRange and resolution apply only to images, that pdfPreset is PDF-only, or what the tool returns after export.

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 covers all parameters with descriptions and an enum for format, so the baseline is 3. The description adds no additional parameter-level meaning, but the schema already provides sufficient detail for parameter understanding.

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'), the resource ('active document'), and the destination ('a specific format'). It is more specific than a tautology, but it does not explicitly distinguish itself from sibling tools like export_pdf, export_image, or batch_export, so the differentiation is left for the agent to infer.

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 gives no guidance on when to choose quick_export over alternatives such as export_pdf, export_image, or batch_export. There is no statement about conditions, exclusions, or trade-offs, leaving the agent without sufficient context for tool selection.

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