protogen__export_cad_design

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

No annotations are provided, so the description carries full burden. It only states the export action but does not disclose side effects, permissions, cost implications, or whether the operation is read-only. For a tool with no annotations, more detail is needed.

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 short (15 words plus a prefix) but the prefix '[protogen — MCP CAD services (measure -> CAD)]' is somewhat redundant and takes up space. The core description is concise but could be better structured without the prefix.

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 no output schema and only 2 parameters with zero schema description, the description should explain return values or constraints. It does not cover what the export produces or any error conditions, making it incomplete for a tool with sparse structured metadata.

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 schema has 0% description coverage, so the description must add meaning. It mentions the three export formats, providing some context for the 'export_format' parameter, but does not list valid values or explain the required 'design_id'. It adds partial value but leaves gaps.

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 the tool exports a CAD design and lists three specific output types (OpenSCAD, STEP contract metadata, manufacturing brief). It distinguishes itself from sibling tools like protogen__generate_cad_design or protogen__manufacturing_plan_from_spec by focusing on the export action.

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 guidance on when to use this tool versus alternatives, nor does it mention prerequisites or when not to use it. It implicitly assumes the design is ready for export but offers no explicit context.

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