drawing_render

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

Annotations declare readOnlyHint and openWorldHint=false, so safety is covered; the description adds behavioral context beyond that (output is a PNG path to be opened with an image reader, dimensions are vectorised and not text-searchable, grid+origin draws a graduated grid in part mm). It omits auth/error behavior, but adds real value over the annotations.

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?

Purpose leads, then usage and practical technique follow; all four sentences carry information. It is dense but largely waste-free, with only minor cramming of several ideas into single sentences.

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 8 parameters and no output schema, the description does the needed work of explaining that the return is a PNG path to be viewed externally, and covers the key region/dpi/grid/origin behaviors. It leaves vector-only input and error handling implicit, so it is strong but not exhaustive.

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 100%, so the baseline is 3, but the description adds interpretation the schema does not: region and higher dpi work together for zoom, and grid requires origin to produce the graduated scale. This clarifies parameter interactions rather than restating definitions.

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 a page or region of a PDF drawing to a PNG and return its path. It also implicitly distinguishes itself from text-search/extract siblings by noting dimensions are vectorised and must be read by eye.

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?

Gives clear when-to-use (locate views, read dimension values by eye) plus tactical guidance (zoom with region + higher dpi for small annotations). It never names a specific alternative sibling such as drawing_extract_geometry, so it stops short of the explicit when-not/alternatives level.

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