render

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It openly conveys that output includes a text digest and metadata, that OpenSCAD draws a blank scene and exits 0 on failed asserts/unknown modules, that auto-fit views have no absolute scale, and that image_size impacts token usage. These are meaningful behavioral traits beyond simple function, though it does not explicitly state read-only status or rate limits, so a 4 fits.

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?

Every sentence in the description contributes substantive information—there is no fluff. However, it is one long dense paragraph with no bullet points, headers, or separation of modes, which makes it harder to parse. For a tool with 22 parameters, structured formatting would help, so it earns a 3.

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 (22 parameters, no output schema, no annotations), the description covers a large amount of core behavior: output structure, error caveats, all main modes, and many parameters. But it leaves out several parameters and does not explain the full relationship between inputs (e.g., scad_file vs scad_content, variables) or any return format details beyond the textual metadata. It is sufficient for basic use but not exhaustive.

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 compensate. It does add meaning to many parameters: views defaults and choices, section expression syntax, parts structure, compare mechanism via variables_after/scad_content_after, grounded scale, annotate contents, look_at forms, callouts, quality values, and image_size token estimate. However, it omits several parameters such as camera_up, include_paths, color_scheme, and camera_target, leaving them to inference, so a 4 is appropriate.

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 states the tool produces images of a model with a text digest and metadata, and enumerates the main modes (views, section, parts, compare). It is specific about the resource and output format, but it does not explicitly mention how it differs from siblings like export_model or model, so it loses a point for lacking sibling differentiation.

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 gives within-tool guidance on when to use different modes and parameters (e.g., grounded=true for orthographic views, compare for before/after), but it never addresses when to choose render versus an alternative sibling tool. There is no mention of alternatives or exclusions, so cross-tool usage guidance is absent.

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