render_preview

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

Annotations are absent, so the description carries the full behavioral burden. It discloses the two output artifacts, but says nothing about whether rendering is synchronous or long-running, whether it fails on a stale/invalid cad_job_id, whether it overwrites prior renders, or what permissions/costs are involved.

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?

A single compact sentence with the action front-loaded and the outputs appended; no filler or redundant restatement of the tool name.

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?

With no annotations, an undocumented two-parameter schema, and a render step that is likely expensive or asynchronous, the definition is too thin. The output schema covers return shape, but prerequisites, failure modes, and parameter meaning are all missing.

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% for both parameters, so the description needed to compensate and does not. Neither design_id nor cad_job_id is explained, and the link between "existing FreeCAD export" and cad_job_id is only vaguely implied.

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 and resource ("Render an existing FreeCAD export with Blender") and names the artifacts produced (PNG and editable blend). It is distinguishable from siblings like export_cad or inspect_design, though it never explicitly frames itself as the step that follows an export.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The word "existing" faintly implies a prior export must exist, but the agent must infer the prerequisite instead of being told to run export_cad first or to choose this over inspect_design.

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