Verifies host environment for required OpenSCAD CLI, default fit tolerances, and supported reference objects to prevent CAD generation failures.
Checks host environment for optional OpenSCAD CLI installation, default fit tolerances, and supported optical reference objects.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. The verb 'Checks' implies a read-only diagnostic operation, and the description lists what is examined, but it does not state whether the tool modifies anything, what happens if OpenSCAD is missing, or what kind of result is returned.
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 well-structured sentence that leads with the action verb and resource, then lists three distinct checks. There is no wasted wording or repetition of the tool name.
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 diagnostic tool, the description names the core checks, but with no output schema and no annotations, it leaves out what the tool returns and how an agent should act on the result. It also does not explain domain-specific terms like 'default fit tolerances' or 'supported optical reference objects'.
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 has zero parameters and 100% schema coverage, so there is no parameter information for the description to add. The baseline for a parameterless tool is 4, and the description appropriately focuses on behavior rather than input semantics.
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 uses the specific verb 'Checks' with a clear resource: the host environment, and enumerates three concrete subjects: OpenSCAD CLI installation, default fit tolerances, and supported optical reference objects. This clearly distinguishes it from the generation, inspection, and calibration siblings.
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?
The description implies a preflight/diagnostic usage context by saying it 'checks host environment', but it never explicitly states when to call this tool before the cad_generate_* or cad_inspect_stl tools, nor does it mention any exclusions. The usage is inferable but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.