new_assembly

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

With no annotations, the description carries full burden. It discloses that it creates and activates a new empty assembly using a default template, returns a dictionary with specific fields, and notes that it does not launch SolidWorks. It does not mention potential side effects like unsaved changes, but for a 'new' operation this is acceptable.

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 three sentences in Spanish and English, front-loaded with the main purpose, includes return value specification and a caveat. No wasteful words.

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 parameters, no output schema, and no annotations, the description is complete: it explains what the tool does, what it returns, and a prerequisite. It covers all needed information for an agent to decide and invoke correctly.

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 input schema has zero parameters, so the description does not need to explain parameters. Baseline for 0 parameters is 4. The description adds no parameter information since none exist.

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 uses a specific verb 'Crear' (Create) and resource 'ensamble nuevo y vacío (documento .SLDASM)' and explicitly distinguishes it from siblings like new_part by specifying it's an assembly. It clearly states the purpose as the starting point for inserting components and mates.

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 provides clear context: it is the starting point for assembly creation. It includes a caveat that SolidWorks must already be running, which is a usage prerequisite. However, it does not explicitly state when not to use it or mention alternatives among siblings.

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