render_drawing

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, and it says almost nothing: it does not confirm the operation is read-only/non-mutating, does not say what is returned (inline bytes, file path, URL), and does not cover error cases like a document not being open. Only the output image formats (PNG/JPG) are disclosed.

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?

It is a single sentence with no padding, so length is appropriate. But the wording is awkward and inward-facing ('to look at it'), which weakens the front-loading of actionable meaning.

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 no annotations, no output schema, and zero schema coverage, the description is too thin: it leaves the return payload, the meaning of the required path, and the operational preconditions unspecified.

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, and it partially does by defining zoom_mm as a corner-pair region in sheet millimeters with the [[x1,y1],[x2,y2]] format. The required path parameter is not explained at all, leaving half the parameters undocumented.

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 conveys that it renders a PNG/JPG of the drawing sheet, which is a recognizable verb+resource. However, it never says 'render' or names the resource as a drawing, and it does not distinguish itself from close siblings like screenshot, drawing_file, or make_drawing. The purpose is inferable but not sharp.

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?

It implies two modes (full sheet vs. a zoom region) but gives no guidance on when to prefer this over screenshot or drawing_file, nor on prerequisites such as an open/active drawing. Usage must be guessed.

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