render_model

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

No annotations are provided, so the description carries the full responsibility. It usefully discloses two non-obvious behaviors: parts are simplified (round and non-catalog parts render as boxes) and reference_image prepends the source picture as the first panel. However, it says nothing about whether output is an image, a file path, or a side effect, which is important for a render tool with zero annotation coverage.

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?

Front-loaded with the core action, then dense but relevant detail about views and reference_image. Slightly run-on with the inline angle list, but every clause carries information.

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?

No output schema exists, so the description should clarify the return form, and it does not say whether rendering produces an image file, a path, or an inline preview. Combined with the undocumented 'size' parameter, the definition is adequate for calling but incomplete for predicting the result.

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 coverage is 0%, so the description must compensate. It does well for two of three parameters: views enumerates the valid named angles and the 'azimuth,elevation' degrees form, and reference_image's effect is explained. The 'size' parameter is never addressed, leaving a gap at this coverage level.

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?

States a specific verb+resource ('Render a preview sheet'), which is clear enough to distinguish it from the other model/part manipulation siblings. It does not name an alternative rendering/inspection tool, nor contrast with describe_model or check_model, so sibling differentiation is only implied by the noun 'preview sheet'.

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 documents default views but never states when to reach for this tool versus describe_model or check_model, nor any preconditions (e.g., a model must be open). Usage is only implied by the 'preview' framing.

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