Set Clear Semi Diameter Margin

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not explain what the 'margin' controls (e.g., a buffer applied around the clear semi-diameter during surface sizing), what units it takes, whether it is persisted to the file, or what side effects it has.

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 short sentence with no filler, but the brevity reflects under-specification rather than efficient structure. It is front-loaded by default since there is only one clause.

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 no annotations, no output schema, and a domain-specific concept ('clear semi-diameter margin') that many agents will not know, the description is too thin to support correct invocation. It does not say what the value represents numerically or how it affects the optical model.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description adds no meaning beyond the schema's terse 'Margin value' text, but the schema already documents the parameter's existence and type.

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 is essentially the tool name with underscores removed: 'Set the clear semi-diameter margin.' It states a verb and a resource but adds no information beyond the title, and it makes no attempt to distinguish itself from the sibling zemax_get_clear_semi_diameter_margin, which it directly mirrors.

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 setter, no mention of its getter counterpart, and no indication of prerequisites such as a loaded/open lens file. The agent must infer all usage context from the name alone.

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