Generate VBA code to create assembly mates in SOLIDWORKS, automating repetitive mating operations for parametric assembly setup.
Generate VBA code for assembly mate creation.
| 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?
No annotations exist, and the description provides no behavioral details such as prerequisites, side effects, or whether it requires an open assembly. The description carries the full burden but fails to disclose these aspects.
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 very short (one sentence) and front-loaded with the clear purpose. Every word serves a purpose, though it could be expanded slightly without losing conciseness.
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 presence of an output schema and nested objects, the description should explain what the output contains and how to structure input data. The current description is too minimal for a tool among many similar VBA generation siblings.
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?
Although schema coverage is 100%, the only parameter, input_data, is described generically as 'The input data value.' The tool description does not clarify what data is expected or how it should be structured, adding little meaning beyond the schema.
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 generates VBA code for assembly mate creation, using a specific verb and resource. However, it does not differentiate this tool from similar siblings like generate_vba_assembly_insert.
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 other VBA generation tools (e.g., generate_vba_extrusion, generate_vba_assembly_insert). The description implies its purpose but lacks context or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.