compare_renders

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

No annotations are provided, so the description carries the full burden. It discloses parallel rendering, use of the render_scad_to_png helper, and QUALITY_PRESETS, but does not cover edge cases like conflicting parameters or error behavior. This is moderate transparency.

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-organized with clear sections and front-loaded purpose. It is somewhat lengthy, but every sentence earns its place given the absence of schema descriptions and the need to explain two usage modes.

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 complex 8-parameter tool with no annotations or output schema, the description is largely complete: it covers modes, all parameters, defaults, and return type. It misses explicit mutual-exclusion details, but overall it is sufficient for an agent to invoke 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?

With 0% schema coverage, the description compensates by documenting all 8 parameters with defaults, valid view presets, image_size format options, and quality presets. This adds substantial meaning beyond the bare input 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 begins with a specific verb+resource: 'Render two versions of a model for visual comparison.' It clearly differentiates from sibling tools like render_single and render_perspectives by focusing on comparison of two versions.

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 explicitly documents two distinct usage modes with exact parameter combinations, giving clear context for when to use each. It does not explicitly name alternatives or exclusion conditions, but the mode breakdown is strong enough for an agent to determine appropriate use.

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