Export Gerber

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

Annotations already disclose that this is a destructive operation (destructiveHint=true) and readOnlyHint=false. The description adds that files are written to a directory and optional components, but it does not mention overwriting, required board state, or other side effects. This is acceptable but not rich.

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 a single, efficient sentence that front-loads the core action and follows with optional modifiers. Every word earns its place, with no filler or 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?

The tool is a straightforward export operation with a clear purpose and output schema. It does not explicitly mention that it exports the current board, but this is implied by the PCB design context. Given the parameter schema and annotations, the description is mostly complete for effective use.

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 parameters are already documented. The description adds a summarized context for optional drill files, map files, and layer subset, but does not explain useAuxOrigin or useProtelExtensions beyond what the schema provides. Baseline 3 is appropriate.

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 a specific verb and resource: 'Export PCB Gerber manufacturing files to a directory.' It distinguishes from siblings by mentioning optional drill files, map files, and layer subset selection, differentiating it from drill-only and single-layer export tools.

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 implies usage context—when you need Gerber manufacturing files—but does not explicitly state when to use this tool versus alternatives like export_drill or export_gerber_single. No exclusions or explicit alternative references are provided.

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