render_single

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

With no annotations provided, the description carries the behavioral burden. It discloses the return format ('List containing the rendered PNG image and metadata'), the mutual exclusivity behavior, and that user-provided variables override quality preset values. It also details accepted input types for camera and image parameters. It does not, however, mention error behavior, file-system access implications, or any side effects beyond what is directly described.

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 long but exceptionally well-organized. It leads with a one-sentence summary, then an Args list with each parameter on its own line, followed by a Returns section. Every entry adds meaningful detail, and there is no redundant or filler content. For a tool with 12 parameters, this length is appropriate and readable.

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 tool's complexity (12 parameters, no annotations, no output schema), the description is remarkably complete. It covers all parameter semantics, default values, return format, mutual exclusivity, and behavioral nuances like quality override rules. The only minor omission is explicit error-handling behavior, but this does not prevent an agent from using the tool correctly.

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 0%, so the description must fully compensate. It does this thoroughly, explaining each parameter's purpose, accepted formats, and defaults. For example, camera_position accepts a list, JSON string, or dict; image_size supports list, string 'widthxheight', or tuple; quality presets are enumerated with their trade-offs. This goes far beyond the bare 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 opens with 'Render a single view from OpenSCAD code or file,' using a specific verb and resource. The phrase 'single view' clearly distinguishes this tool from sibling render_perspectives, which would produce multiple views, and from validation or model tools.

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 clear context for when to use the tool: whenever a single render of OpenSCAD code or a file is needed. It also explains key usage constraints, such as scad_content and scad_file being mutually exclusive, and parameter defaults. However, it does not explicitly name alternative tools for other use cases (e.g., render_perspectives for multiple views), nor offer exclusions beyond the mutual exclusivity.

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