render_single

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

With no annotations provided, the description carries full burden. It reveals this is a rendering operation that produces images, mentions the return format (dict with base64 PNG or file path), and implies computational intensity through numerous camera/view parameters. However, it doesn't disclose important behavioral aspects like execution time, resource requirements, error conditions, or what 'auto' output format means in practice.

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 well-structured with clear sections (purpose, args, returns) and uses bullet-like formatting for parameters. While comprehensive, some sentences could be more concise (e.g., the camera parameter explanations are repetitive). The front-loaded purpose statement is clear, but the parameter documentation dominates the description length.

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 the complexity (11 parameters, no annotations, 0% schema coverage), the description does a good job explaining parameter semantics and the return value. The output schema exists, so the description appropriately focuses on what the tool does rather than return structure. However, for such a complex rendering tool, more behavioral context about performance, limitations, or typical workflows would be beneficial.

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?

With 0% schema description coverage and 11 parameters, the description provides extensive semantic value beyond the bare schema. It explains the mutual exclusivity of scad_content/scad_file, enumerates valid 'view' options, details multiple acceptable formats for camera parameters and image_size, lists output_format options with their default, and clarifies what 'variables' represents. This significantly compensates for the schema's lack of descriptions.

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 verb ('Render') and resource ('a single view from OpenSCAD code or file'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'check_openscad' - both involve OpenSCAD but for different purposes (rendering vs checking).

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 provides no guidance on when to use this tool versus alternatives. While it mentions the mutual exclusivity of 'scad_content' and 'scad_file', this is parameter-level guidance, not tool-level guidance about when to choose render_single over other rendering or OpenSCAD tools. No context about prerequisites or typical use cases is provided.

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