render_drawing

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

No annotations are provided, so the description carries the full burden. It discloses the underlying library (resvg-py), explains that the PNG is returned inline for LLM viewing, and mentions width default and aspect ratio height. However, it does not disclose potential side effects, auth requirements, error handling, or the exact format of the inline PNG data.

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 well-structured with a brief intro, a complement relation, and an Args section. It is front-loaded with purpose. The Args section repeats schema info but adds useful context. It could be slightly more concise, but overall it is efficient and well-organized.

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?

Given 3 parameters, no enums, no nested objects, no output schema, and no annotations, the description covers the tool's function well. It explains the sibling relationship, inline return, and parameters. However, it lacks details on return format (e.g., MIME type) and potential errors, which would make it more complete.

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 must compensate. It provides clear explanations for each parameter: svg_path is the path to the SVG file, width includes default and height set by aspect ratio, and save_to is an optional path with fallback to inline delivery. This adds significant meaning beyond the bare schema.

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 it rasterizes an SVG to PNG via resvg-py, and explicitly distinguishes from sibling tool render_view by explaining that render_drawing accepts an SVG written outside the sandbox while render_view takes build123d shapes from the live session.

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?

The description explicitly tells when to use this tool (for SVGs written outside the sandbox) vs render_view (for build123d shapes). It also describes the typical workflow of a short Python script doing ExportSVG. However, it does not explicitly state when not to use it.

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