Render OpenSCAD source to a PNG image

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that the tool renders to PNG and supports camera control, but does not mention error handling, execution characteristics, or the relationship between cameraPreset and cameraPosition when both are provided. It adds some value over the schema but leaves gaps.

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 two sentences, with the main purpose front-loaded in the first sentence and parameter usage summarized efficiently in the second. No unnecessary words or repetition of schema details.

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 5 parameters including an enum and nested object, the description covers all key inputs (scadCode, width/height, camera options) and states the output as PNG. Since an output schema exists, return values are documented elsewhere. It could mention what happens on invalid code or if both camera options are provided, but overall it is complete enough for a simple render tool.

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%, so the schema already documents all parameters. The description restates the parameters in prose but does not add new semantic details beyond what the schema provides, such as default values or the precedence rule between cameraPreset and cameraPosition (which is partially in the schema).

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 clearly states the tool renders OpenSCAD source code into a PNG preview image, using a specific verb ('render') and resource ('SCAD source code'), and distinguishes from the sibling tool by mentioning PNG output (vs STL). This makes the purpose unambiguous.

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 explains how to use the tool (provide scadCode, set optional width/height/camera options) but does not explicitly state when to choose this over export_scad_stl or mention any exclusions. The usage context is implied by the word 'preview' but not made explicit.

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