zemax_nsc_convert_to_nonsequentialConvert the current optical system to non-sequential mode in Zemax, switching from sequential ray tracing to NSC geometry for stray light and illumination analysis.
Convert or make the current optical system non-sequential.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It doesn't disclose whether the conversion is reversible, what happens to existing sequential data, whether it requires a saved system, or any side effects. 'Convert or make' is vague about mutation semantics.
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?
One short sentence that is front-loaded and wastes no words. Slightly terse given the state-changing nature of the operation, but structurally fine.
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?
A mutation tool with no annotations, no output schema, and no behavioral disclosure is under-specified. The description should at least state that it changes the system mode and whether it is reversible.
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?
Zero parameters, so baseline is 4 per the rubric. No parameter details are needed and none are missing.
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 (convert) and resource (optical system to non-sequential), and the sibling zemax_nsc_convert_to_sequential makes the direction clear. However it doesn't explicitly differentiate itself from that sibling in the text.
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 when-to-use guidance, no prerequisites, no mention of the inverse sibling tool or when to prefer it. The agent must infer usage entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.