Export OpenSCAD source to an STL

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

With no annotations provided, the description must disclose behavioral traits, but it only mentions the return format as an 'embedded resource blob'. It does not discuss prerequisites (e.g., OpenSCAD installed), error cases, or any side effects, leaving significant behavioral ambiguity for a tool with no annotation support.

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, front-loaded sentence that directly states the tool's function and return format. Every word is purposeful and there is no redundant information or filler.

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 simple two-parameter tool with a complete schema and output schema available, the description covers the core functionality and return format. It might benefit from a note about the filename being optional or the rendering process, but these are not essential given the schema and output schema richness, making the description reasonably complete.

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 input schema has 100% coverage with descriptions for both parameters, so the baseline is 3. The description adds minimal semantic value beyond the schema; it implies scadCode usage by mentioning 'OpenSCAD (SCAD) source code' but does not clarify filename defaults or behavior, which the schema already documents.

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 a specific verb 'Export' and identifies both the input (OpenSCAD source) and output (STL), clearly distinguishing this from the sibling tool render_scad_png which produces PNG images. The intent is 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 implies usage when an STL file is needed from OpenSCAD code, but it does not explicitly mention the sibling tool or provide when-not-to-use guidance. It gives a clear context but lacks exclusions or alternative tool references, putting it at the implied usage level.

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