Open File

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

No annotations are provided, so the description carries full behavioral burden. It states the operation but does not disclose side effects such as whether opening replaces the current system, what happens if the file is missing, or whether a connection is required.

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?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized, though the brevity contributes to missing usage and behavioral context.

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 file-opening tool with no annotations and no output schema, the description is too sparse. It omits whether a connection is required, what opening does to the current lens system, how path and filePath differ in practice, and when to use this instead of zemax_new_system or zemax_connect.

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%, and the schema explains both parameters as absolute lens-file paths, including the legacy versus Windows distinction. The description adds only the supported file extensions, so the baseline of 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?

The description states a specific verb and resource: 'Open a Zemax .zmx or .zos lens file.' It clearly identifies the action and supported file types, but does not distinguish this tool from siblings such as zemax_close_file, zemax_save_file, or zemax_new_system.

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?

There is no guidance on when to use this tool versus alternatives like zemax_connect, zemax_new_system, or zemax_restart. It also omits prerequisites such as whether a Zemax session must already be connected.

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