create_technical_drawing

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

No annotations are provided, so the description must fully disclose behavior. It mentions creation from a part/assembly and supported options but fails to state whether the model file is required, what happens if not provided, or any error conditions. The behavior regarding active document vs. explicit file is unclear.

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 consists of two concise sentences, with the main action front-loaded. No unnecessary words or repetitions. Efficiently communicates core purpose.

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 complexity of nested parameters and presence of an output schema, the description is adequate but lacks important context, such as how the model_file parameter interacts with the active document. Also, no comparison with sibling tools like 'create_drawing' is provided.

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% with descriptions for each sub-parameter. The description adds a high-level summary of selectable parameters (template, output path, etc.), but does not provide deeper semantic context beyond what the schema already conveys.

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 creates a technical drawing from a SolidWorks part or assembly, listing supported options. However, it does not explicitly differentiate from the sibling 'create_drawing', which may have overlapping functionality, causing potential confusion.

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?

There is no guidance on when to use this tool versus alternatives like 'create_drawing', 'create_drawing_view', or other drawing-related tools. The description does not specify prerequisites (e.g., model must be open) or exclusions.

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