render_drawing

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

Annotations already indicate readOnlyHint=true. The description adds that the PNG is returned inline and that width uses a default of 1200 with height determined by aspect ratio, using the resvg-py library. It does not detail potential issues like file not found or large file limits, but the key behaviors are covered.

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 efficient, consisting of a concise opening sentence, a contrast with a sibling, a note on return method, and a clear Args section. Every sentence adds value with no redundancy.

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 simple conversion tool with no output schema, the description covers the essentials: purpose, input parameters, comparison to a sibling, and return behavior. It could mention error handling or format details, but it is largely sufficient.

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?

The schema has no parameter descriptions (0% coverage). The description compensates fully by explaining each parameter: svg_path is a file path, width is pixel width with aspect ratio scaling, save_to optionally writes the PNG to disk. This adds clear meaning beyond the raw 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 file to PNG, and distinguishes from the sibling tool render_view by noting that render_drawing accepts an external SVG file, while render_view uses 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 explains when to use this tool (when you have an SVG file written outside the sandbox) and contrasts it with render_view. However, it does not provide explicit guidance on when NOT to use it or mention other alternatives from the sibling list.

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