New System

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It doesn't disclose whether creation resets/discards an existing system (destructive), whether it requires a prior zemax_connect, or what happens to current state. For a session-initializing mutation, 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?

A single front-loaded sentence that conveys verb, object, and the two modes. No waste.

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?

Adequate for a simple initializer, but with no annotations it omits behavioral essentials: state-reset semantics, connection prerequisites, and whether an existing model is overwritten. These are exactly the details an agent needs before creating a new system.

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 coverage is 100% and there is only one optional parameter with a default and description, so the schema already explains 'sequential'. The description adds no param detail but doesn't need to; baseline for fully covered params is high.

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 (Create) and resource (blank optical system) with a mode discriminator (sequential or non-sequential). It does not distinguish itself from siblings like zemax_nsc_convert_to_nonsequential, but the purpose is clear from the description alone.

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 guidance on when to use this initializer versus alternatives such as zemax_open_file or the nsc_convert_* tools. The agent must infer that this is for creating an empty system from scratch.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.