render_view

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

With no annotations, the description must disclose behavior. It reveals the output is a clean PNG and explains the framing behavior. However, it does not mention side effects like file creation, overwrite behavior, or the meaning of the required 'path' parameter, leaving key behavioral details implicit.

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?

Two sentences, no fluff. The first states purpose and key output feature; the second gives precise parameter usage. Every word earns its place.

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?

The description covers the core purpose and the optional window framing, but lacks details about the required 'path' parameter and coordinate system ordering (e.g., lower-left vs upper-left). Since an output schema exists, return values need not be explained, but the missing path semantics and potential side effects leave completeness gaps for an agent.

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 explains the four coordinate parameters (x1,y1,x2,y2) as a window, but the required 'path' parameter is not explained. This is a significant gap since 'path' is the only required parameter, though the phrase 'render to a clean PNG' hints it is the output file path.

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 verb 'Render' and the resource 'the drawing to a clean PNG', specifying the output format and purpose ('for visual inspection'). It distinguishes itself from sibling tools like export_pdf and export_dxf by emphasizing the PNG output with no UI chrome.

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?

Provides clear usage context: 'for visual inspection' and explains how to frame a region with the window parameters, including the alternative of omitting for the current view. It does not explicitly name alternatives or exclusions, but the intended use case is clear.

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