Spot Diagram

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only notes that analysis is for one field. It does not state whether the tool is read-only, whether it returns data or opens a window, what permissions are required, or any side effects.

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 description is a single efficient sentence with no wasted words and the action is front-loaded. It is appropriately concise for a one-sentence definition, though its extreme brevity borders on under-specification for the tool's complexity.

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?

Given no annotations, no output schema, and an analysis tool with three parameters, the description is too sparse. It omits prerequisites (e.g., a loaded system), return format, and any distinction from sibling spot-analysis tools, leaving the agent with minimal context beyond the name and schema.

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 schema already explains each parameter (one-based field, Gaussian rings, 0 for polychromatic). The description adds only the phrase 'for one field', which aligns with the field parameter but provides no extra syntax or format detail, so baseline 3 is appropriate.

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 specific verb ('Calculate') and resource ('spot-size analysis') and adds scope ('for one field'). It is clear what the tool does, but it does not differentiate from sibling tools like zemax_rms_spot or zemax_spot_rms, which likely produce related spot metrics.

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 such as zemax_rms_spot, zemax_ray_fan, or zemax_geometric_image_analysis. The only usage hint is the implicit 'one field' scope, which is insufficient for selecting among related analysis tools.

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