solidworks_new_document

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, covering the mutation/safety profile. The description adds meaningful context: the template path must be absolute and existing, and the tool returns a handle to the created document. This goes beyond what annotations state without contradicting them.

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?

A single, information-dense sentence that front-loads the action and result. No filler or redundancy; every word contributes to understanding.

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?

The description covers the core operation and return value, and an output schema exists to define the response. However, it does not mention how to obtain a valid template path (e.g., via solidworks_templates) or potential error conditions. Given the tool's simplicity and the presence of an output schema, this is adequate but not exhaustive.

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 zero description coverage for the 'template' parameter. The description provides some meaning by specifying 'absolute existing template path', but it does not clarify acceptable file extensions or further constraints. For a single-parameter tool, this is a partial compensation but not complete.

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?

States a specific verb 'create' with resource 'part/assembly/drawing' and scope 'from an absolute existing template path', clearly distinguishing it from open_document (which opens existing) and templates (which lists). An agent can tell it apart without needing to inspect other tools.

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 implies this tool is for creating new documents from a template path, but it does not explicitly mention when not to use it or name alternatives like solidworks_templates for discovering valid paths. The context is clear enough that an agent can infer the use case, but explicit routing is absent.

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