pcb_export_render_png

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 only discloses the cairosvg dependency. It does not mention whether the tool requires an active session (implicit via session_id), what happens if the output file exists, or the return behavior. This is minimal disclosure for a tool with side effects (file creation).

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 two sentences, front-loaded with the main purpose and followed by an essential dependency note. Every word earns its place, with no filler.

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 an 8-parameter tool with 100% schema coverage, the description is adequate but lean. It lacks guidance on choosing this over pcb_export_all_renders and does not mention the return value (e.g., the output path). The missing output schema and minimal description leave some context gaps.

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 100%, so the baseline is 3. The tool description does not add any param-specific semantics beyond what the schema already provides. It mentions render types, but the schema already enumerates them. No added value.

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 uses a specific verb ('Export') and resource ('SVG render to PNG'), explicitly listing the supported render types (board, stackup, net, annotated). This clearly distinguishes it from sibling tools that render or annotate but do not export to PNG.

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 does not provide any guidance on when to use this tool versus alternatives like pcb_export_all_renders. No exclusions, prerequisites, or context (e.g., 'use this when you need a single PNG') are given. The only implied usage is from the tool name and description.

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