Zrd Read

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

No annotations are supplied, so the description carries the full behavioral burden. 'Read' and 'bounded' hint that this is a non-mutating, size-limited operation, but the description never confirms it does not modify the file, what the bounds default to, or what happens when the limits are hit. For a read tool with zero annotation coverage this is thin.

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 padding or redundancy. It is efficient, though so terse that it omits useful context rather than being verbose.

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?

There is no output schema and the description never explains the 'nested ray and segment sample' return structure, which is the most ambiguous part of the tool. Combined with no annotations and no usage guidance, an agent lacks what it needs to interpret results or decide when to call it.

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 filePath, filter, maxRays and maxSegments are already documented in the schema and the baseline is 3. The description adds no syntax, format, or default-value detail beyond what the schema provides.

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 gives a concrete verb ('Read') and resource ('a ... ray and segment sample from a ZRD'), scoping the operation to a bounded portion of the file. It is clear what the tool retrieves, though it never names or differentiates itself from the sibling zemax_zrd_summary, which an agent must infer operates on the same ZRD files.

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 statement of when to use this tool versus zemax_zrd_summary or the other NSC ray-trace tools, nor any prerequisite guidance (e.g., that a ZRD must already exist from a prior trace). The 'bounded sample' phrasing implies a use case but the agent gets no explicit routing help.

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