save_part

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the agent knows this mutates state; the description adds nothing about what is destroyed or that an existing target is refused by default. The units sentence (mm, degrees, kg) is irrelevant to a file-save operation and the closing phrase "inspect verified measurements and error evidence" is opaque and hints at return content for which there is no output schema.

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?

It is short and front-loaded with the verb, but two of three sentences contribute little: the unit-conversion note is unrelated to saving, and the closing clause about "verified measurements and error evidence" is vague filler. Trimming to the save behavior plus overwrite/path semantics would be stronger.

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?

This is a destructive, non-idempotent file-writing tool with no output schema and only half its parameters documented in the schema. Such a tool needs the description to explain target path semantics, default refusal of existing files, and what is returned on success or failure; the definition omits all of it.

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?

Schema description coverage is only 50%: `path` has no description at all, and the description never mentions either parameter or clarifies path format (absolute vs relative, extension, directory must exist). The useful overwrite semantics live entirely in the schema, so the description compensates for none of the coverage gap.

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 first sentence restates the name almost verbatim ("Save part") with the addition of "through the independent native SOLIDWORKS engine," which is engine branding rather than functional detail. It never says the part is written to a file path on disk, which is the actual operation implied by the required `path` parameter. It also makes no attempt to distinguish this from siblings like save_assembly, close_part, or export.

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?

There is no guidance on when to save versus export, save_assembly, or close_part, nor any prerequisite context (must a document be active/open?). The conditions selecting `overwrite` are only described inside the schema, not in the description.

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