Nsc Detector Viewer

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

No annotations are provided, so the description carries the full burden. 'Bounded' hints at the maxCells limit but is not explained, and nothing is said about permissions, side effects, whether it mutates the system, or what the extraction returns for scalar vs RGB data.

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 filler. It is efficient, though arguably too terse for a seven-parameter tool with no annotations.

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?

With 7 parameters, no annotations, and no output schema, the one-sentence description is insufficient. It omits when to use it, how the bounded extraction behaves, and how it relates to the many sibling detector tools.

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% with 7 documented parameters, so the baseline is 3. The description's 'scalar or RGB data' loosely gestures at dataType/showAs but adds no concrete meaning beyond the schema.

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 verb ('extraction') and resource ('Detector Viewer') plus the data scope ('scalar or RGB'). However, it never distinguishes this tool from close siblings such as zemax_nsc_detector_data, zemax_nsc_detector_pixel, or the polar variants, and 'bounded' is left unexplained.

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 when-to-use guidance, no prerequisite (e.g. an open detector object), and no named alternative. The agent must infer from the name alone when this viewer tool should be picked over detector_data, detector_pixel, or load/save_detector.

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