pcb_export_all_renders

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

With no annotations, the description carries the burden and does disclose the key side effect (writing PNG files to a directory) and the return shape (label-to-file-path mapping). It does not mention directory creation/overwrite behavior or potential failure modes, leaving some behavioral uncertainty for an exported filesystem write operation.

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?

A single well-structured sentence states the action, the included render set, the output format/location, and the return value. No filler or redundant restatement of schema fields.

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 a simple 3-parameter schema, no annotations, and no output schema, the description adequately covers what the tool does and what it returns. Minor gaps remain around file creation details, but the core selection-and-invocation context is present.

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 description need not repeat parameter details. It adds helpful context by introducing the concept of labels and standard render types, but does not deepen semantics for width_px, output_dir, or session_id beyond the schema descriptions.

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?

Description uses specific verb 'Generate and export all standard renders', enumerates exact asset types (board, stackup, key nets, annotated findings), and specifies PNG output to a directory. This clearly distinguishes it from individual render/export siblings like pcb_render_board and pcb_export_render_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 phrase 'all standard renders' establishes clear context for batch use versus individual render tools, and the return mapping implies a complete export workflow. However, it does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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