zemax_set_number_of_wavelengthsSet the number of wavelength rows in an Ansys Zemax OpticStudio model. Use it to define the wavelength count for simulations and analyses.
Set the number of wavelength rows.
| Name | Required | Description | Default |
|---|---|---|---|
| numberOfWavelengths | Yes | Desired wavelength count |
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 the full burden. 'Set' implies mutation but the description says nothing about what happens to existing wavelength rows when count is increased/decreased, whether this is destructive, or whether it requires a connected system. Significant gap for a mutation with no annotation coverage.
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?
Single short sentence, front-loaded with the action and resource. Efficient, though so terse that it omits potentially useful context rather than being overlong.
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 mutation tool with no annotations, no output schema, and a sibling (zemax_set_wavelengths) that could be confused with it, the description is insufficient. It should clarify the count-vs-value distinction and the effect on existing data.
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 parameter's meaning ('Desired wavelength count') is fully documented in the schema. The description adds nothing beyond what the schema already provides, making the baseline 3 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?
States a specific verb and resource: 'Set the number of wavelength rows.' An agent can tell it controls wavelength count specifically. However, it does not differentiate against sibling tools like zemax_set_wavelengths (which sets wavelength values), leaving ambiguity between the two.
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 and no mention of alternatives. The sibling zemax_set_wavelengths exists and is not referenced, so the agent must infer whether to call this to change count vs. to change values.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.