zemax_export_analysisExport Zemax OpticStudio analysis results as text, bitmap, JSON, or CSV files by specifying the analysis type and destination path.
Export an analysis result as text, bitmap, or structured data.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | text, bmp, json, or csv | text |
| filePath | Yes | Destination path | |
| analysisType | Yes | Analysis identifier |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not explain whether analysis results must already exist, whether the export is idempotent, whether it can overwrite an existing file, or return behavior. It only names the output formats.
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?
A single short sentence with the action front-loaded and the format options included. Nothing extra.
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 3-parameter export tool with no annotations and no output schema, the description is minimal. It conveys the basic operation but omits prerequisites (e.g., an analysis must have been run), overwrite behavior, and return handling. Adequate but with clear gaps.
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 coverage is 100%, so all three parameters are already documented in the schema, including the format values. The description adds the format list but nothing beyond the schema. Baseline 3 is appropriate.
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?
Clear verb ('Export') and resource ('an analysis result') with the supported output formats enumerated. It doesn't differentiate from siblings like zemax_save_file, but the verb+resource is specific enough for an agent to understand the operation.
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 on when to use this vs alternatives such as zemax_run_analysis or zemax_save_file, or when each format is appropriate. The description states what it does but not when to choose it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.