zemax_multistart_statusCheck the progress of a running Zemax multistart optimization without blocking, so you can monitor completion status while it continues in the background.
Poll multistart progress without blocking.
| 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?
With no annotations, the description carries the full burden and it discloses one genuine behavioral trait: the call is non-blocking. It omits other important traits such as what happens when no multistart is running, whether it is safe to call repeatedly, or what state the response conveys.
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 no wasted words, with the non-blocking trait placed prominently. Its brevity borders on being too terse for a tool with no supporting schema or annotations, but as structure it is efficient.
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 polling tool with no output schema and no annotations, the description should say more about what the polled status contains (progress, iteration, convergence) so the agent knows how to interpret results. It covers the essence but leaves the return semantics implicit.
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?
The tool takes zero parameters, so there is nothing to document; the baseline for a 0-param tool is 4. The description adds no parameter detail, which is appropriate here.
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 (poll) and resource (multistart progress), which lets an agent distinguish it from the sibling write controls zemax_multistart_optimize and zemax_multistart_stop. It is clear but does not explicitly name those siblings to reinforce the routing.
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?
'Poll ... without blocking' implies this is called periodically during a run, but there is no explicit when-to-use guidance, no statement of prerequisites (e.g. a multistart must be in flight), and no reference to the alternative stop/optimize tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.