solidworks_save

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

It reveals that format support depends on document type and that this tool does not handle export options, going beyond the annotations' destructive hint. It also mentions the workspace context, which is not in the annotations.

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 concise and front-loaded with the primary action, using only two sentences. It avoids unnecessary verbosity while covering the core functionality.

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?

It provides key context about workspace limitation and format support, and directs to SaveAs for advanced options. However, it lacks details about return values and the behavior of the overwrite parameter, which is important for safe usage. Overall adequate for basic usage.

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?

No parameter descriptions are provided in the schema, and the description does not explain the path, document, or overwrite parameters. The agent is left to guess their semantics, especially how the extension in path determines format and what the document parameter defaults to.

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 action (Save/export), the resource (by extension), and provides examples of file types. It distinguishes the tool's scope from advanced export options by directing users to API SaveAs.

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?

It provides a clear condition for when not to use this tool (when export options are needed) by directing to API SaveAs. However, it does not contrast with specific sibling tools like solidworks_open_document or solidworks_exchange.

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