scad_render_views

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds behavioral context about the rendering modes (preview vs. CGAL) and the nature of the output (labeled grid image), which goes beyond the structured annotations. It does not contradict annotations.

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, front-loaded with the main purpose. Every sentence adds value: the first defines the tool, the second gives practical usage details. No redundant or filler content.

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 rendering tool with no output schema, the description should clarify the return format (e.g., how the grid image is delivered) and explain all parameters. It does not mention how the image is returned, and 'size' and custom 'views' are only loosely implied. The description is adequate for a simple tool but leaves some gaps.

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 mentions the 'preview' parameter and lists the default views for the 'views' parameter, but does not explain 'code' or 'size'. This partial coverage is helpful but leaves some parameters under-described.

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's function: 'Render multiple labeled views of an OpenSCAD model into a grid image.' It identifies the specific verb (render), resource (OpenSCAD model), and output (grid image), which distinguishes it from siblings like blender_render_tiled (Blender-specific) and scad_cross_section (cross-sectional views).

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 usage context by specifying default views and instructing to set preview=False for CGAL-rendered final views, which is slower. It does not explicitly list alternatives or exclusions, but the instructions imply when to use different rendering modes. This is clear context without direct alternative comparisons.

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