Render Preview

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds useful detail by saying the output is a verified PNG and that the camera is a numeric 6/7-value array, but it does not explain output behavior, failure modes, side effects, or interpretation of camera values.

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 a single well-structured sentence with a front-loaded action and minimal wasted words. It is concise without being vague in its core purpose, though that brevity does trade away parameter guidance.

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 tool with 9 parameters, no annotations, and no schema coverage in the description, the one-line description leaves significant context gaps. It does not explain what the render_mode preview/render distinction means, how sizing works, how colorscheme affects output, or how the custom camera values are consumed.

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 needs to compensate. It adds meaning for 'view' and 'camera', but the other seven parameters—width, height, version, projection, colorscheme, render_mode, and project_id—receive no semantic explanation beyond their schema names and enums.

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 identifies the action ('Render a verified PNG') and the resource scope: a named view or a numeric 6/7-value custom camera. This gives the agent a concrete sense of what the tool does, though it does not explicitly distinguish the tool from the closely named sibling render_preview_set.

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?

There is no guidance about when to use this tool versus alternatives like render_preview_set or export_model. The description states what it does but not which scenarios call for it or when it should be avoided.

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