Nsc Get Source Spectrum

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but the description does not disclose whether it fails for non-source objects, what happens with an invalid objectNumber, or any permission/state requirements. For a read-only getter this is a modest gap, but nothing beyond the verb is revealed.

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 the term 'typed' is unexplained jargon that slightly reduces immediate comprehension.

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 one-parameter getter with no output schema, the key missing piece is what the returned 'typed spectrum settings' actually contain. Naming the retrieved quantity is minimally adequate, but with no output schema the description should say more about the return shape to be fully complete.

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 single parameter (objectNumber, one-based source object number) is fully documented in the schema. The description only adds the qualifier that the object must be an NSC source, which is marginal value beyond the schema, so baseline 3 applies.

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 (Get) and resource (typed spectrum settings) scoped to an NSC source object. It is clearly distinguishable from its setter sibling zemax_nsc_set_source_spectrum by the Get/Set verb pairing, though it never names that counterpart explicitly.

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?

Provides no when-to-use guidance, prerequisites, or alternatives. An agent must infer that this reads spectrum settings before modifying them, and nothing routes it away from or toward zemax_nsc_get_object or the setter sibling.

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