zemax_set_number_of_fieldsSet the number of field rows in Zemax OpticStudio to define how many field points are used for ray tracing and optimization.
Set the number of field rows.
| Name | Required | Description | Default |
|---|---|---|---|
| numberOfFields | Yes | Desired field 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. It states a mutation but doesn't disclose whether existing field data is preserved, truncated, or requires a connected session. For a state-changing tool with zero annotation support, this is a notable 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?
Single efficient sentence with no waste. It could be improved by front-loading the behavioral implication, but it is appropriately sized.
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 and no output schema, the description is too thin. It omits what happens to existing fields, whether reconnection is required, and how it relates to the zemax_set_fields sibling. The agent lacks enough context to call it confidently.
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 is already documented in the schema. The description adds no syntax, range, or constraint details beyond what the schema provides. 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?
States a specific verb (Set) and resource (number of field rows), which is clearer than the name alone implies. However, it doesn't distinguish from the sibling zemax_set_fields, which likely handles field definitions more broadly. Without opening schemas, an agent may not know which to choose.
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 when to call this instead of zemax_set_fields. The agent must infer from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.