pcb_export_manufacturing

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

With no annotations at all, the description carries the full burden, and it does add one genuinely valuable behavioral fact: human review is still required, so the agent should not treat the export as a final approved artifact. It omits other important traits such as where files are written, whether the export is repeatable/overwriting, and required permissions.

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?

One compact sentence with the action and the downstream caution front-loaded and no filler. It is efficiently sized, though the semicolon clause could have been spent on parameter clarification instead.

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?

There is no output schema and no annotations, so the description is the only source of behavioral detail, and it covers the validation prerequisite and human-review requirement. It still leaves open what the required 'name' means and what the caller receives on success, which matters for a file-producing tool.

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 single parameter 'name' has 0% schema description coverage, and the description says nothing about what 'name' identifies (project name? workspace? output filename?). With one undocumented required parameter, the description fails to compensate for the gap.

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 names a specific verb and resource ('Export Gerber files'), so an agent knows exactly what artifact this produces and can distinguish it from the sibling validation/generation tools. It stops short of explicitly contrasting with pcb_validate_project, but the output artifact is unambiguous.

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?

'after validation' implies a prerequisite ordering relative to pcb_validate_project, which is useful sequencing guidance. However, it never names the alternative tool or states what to do when validation has not passed, leaving the workflow conditional implicit.

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