Generate VBA code based on macro recording patterns to automate SolidWorks operations and build parametric models.
Generate VBA code using macro recording patterns.
| Name | Required | Description | Default |
|---|---|---|---|
| input_data | Yes | The input data value. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behaviors. It only states the purpose; no mention of side effects, idempotency, safety, or what the output represents. The presence of an output schema is not leveraged in the description.
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 sentence, efficient in length, but it lacks key information. Conciseness should not come at the cost of completeness; here it is under-specified.
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 generic input, no behavioral annotation, and numerous sibling tools, the description is insufficient for an agent to understand how to invoke this tool correctly. The output schema exists but is not described, and the description does not cover expected behavior.
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 sole parameter 'input_data' is described in the schema as 'The input data value,' which is vague. The description adds no further meaning, leaving the agent unclear on what data to provide. Schema coverage is 100% but the schema's own description is poor, and the tool description does not compensate.
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 it generates VBA code using macro recording patterns, distinguishing it from general VBA generation (generate_vba_code) or recording (automation_start_macro_recording). However, 'macro recording patterns' is somewhat vague.
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?
No guidance on when to use this tool versus siblings like generate_vba_code, automation_start_macro_recording, or other VBA generation tools. The description provides no context or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.