Nsc Ray Trace

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

With no annotations, the description carries the full behavioral burden and discloses nothing beyond the bare action. It does not mention side effects such as clearing detectors, saving ZRD files, error handling, runtime characteristics, or whether the trace mutates system state.

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 one-sentence description is front-loaded and waste-free, but it is not appropriately sized for a 9-parameter tool with meaningful behavioral choices. It is concise to the point of under-specification.

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?

Given 9 parameters, no annotations, and no output schema, the definition is substantially incomplete. The schema documents parameter names, but the description omits when to use the tool, what happens to detectors or ZRD state, and what to expect from the operation.

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 all 9 parameters are already documented in the schema. The description adds no additional parameter meaning, making the baseline 3 appropriate when the schema does the heavy lifting.

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: 'Run a non-sequential ray trace.' The 'non-sequential' qualifier helps distinguish it from sequential ray tracing siblings, but it does not explicitly differentiate from other ray-trace-adjacent tools like zemax_batch_ray_trace.

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?

The description provides no when-to-use guidance, no alternatives, and no prerequisites. An agent must infer from the name that this is the NSC ray trace tool rather than the sequential zemax_ray_trace or batch variant.

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