Get Clear Semi Diameter Margin

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

No annotations are provided and the description adds no behavioral context such as read-only status, required system state, or that it returns a margin value. It is a pure restatement with no disclosure beyond the name.

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 single sentence is concise but purely tautological, adding no information beyond the title. Conciseness here reflects under-specification rather than efficient communication.

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 zero-parameter getter, the description should at least state what value is returned and its context in an optical design workflow. Without annotations or an output schema, the description carries full burden and fails to provide meaningful context.

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?

The tool takes zero parameters, so the baseline is 4. Schema coverage is 100%, and there are no parameters whose semantics need explanation.

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 restates the tool name almost verbatim ('Get the clear semi-diameter margin'), providing a verb and resource but no additional clarifying detail. It conveys the basic purpose but does not explain what the margin is or how it differs from sibling tools like zemax_get_surface or zemax_get_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. An agent cannot infer from the description whether this is a diagnostic check, a setup query, or a value needed before calling zemax_set_clear_semi_diameter_margin.

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