zemax_set_mtf_unitsSet spatial-frequency units for MTF analysis in Ansys Zemax OpticStudio, ensuring calculations and reports use your required units.
Set MTF spatial-frequency units.
| Name | Required | Description | Default |
|---|---|---|---|
| mtfUnits | Yes | MTF units |
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 behavioral burden, yet it only restates the setting. It does not disclose accepted unit strings, whether the change is global or per-analysis, whether it requires an active model, or what side effects follow.
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, front-loaded sentence with the verb and resource first and zero padding. It is efficient but under-specified rather than overwritten.
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 setter with no annotations and no output schema, the definition omits the valid unit set, the effect scope, and any precondition, leaving an agent unable to call it reliably without external knowledge.
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 100%, so the baseline is 3, and the schema's 'MTF units' label is itself tautological. The description adds only the qualifier 'spatial-frequency,' without enumerating valid strings, so it does not meaningfully enrich the parameter.
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?
States a specific verb (Set) and a precise resource (MTF spatial-frequency units), which cleanly distinguishes it from the sibling zemax_get_mtf_units. However, it does not name the valid unit values or the scope of the setting, so it is clear but not maximally informative.
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?
There is no guidance on when to use this setter versus reading with zemax_get_mtf_units, nor any prerequisite such as needing an open file or loaded MTF analysis. The agent must infer the usage context entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.