kicad.export_gerbers

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

With no annotations provided, description discloses important behavioral constraints: project dependency and DRC gate. However, it omits explicit mention of file creation side effects or overwrite behavior expected of an export 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?

Three sentences are perfectly structured: prerequisite front-loaded, core purpose stated, and operational constraint with remediation included. Zero waste.

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 the existence of an output schema, the description adequately covers operational requirements (project state, DRC checks) for this single-parameter tool. Only gap is the undocumented parameter semantics.

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 0% (output_dir lacks description) and the description fails to compensate by explaining the parameter's purpose, expected format, or relationship to the Gerber files. Context makes it inferable but not documented.

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 states specific action 'Export Gerber manufacturing files' with clear resource type, distinguishing it from sibling export tools (export_bom, export_pdf, export_svg).

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?

Explicitly states prerequisite '[Requires open project]' and blocking condition 'Blocked if DRC has unresolved errors', with explicit alternative action 'run kicad.run_drc first'.

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