save_part

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

There are no annotations, so the description carries the full burden. It clearly states the core write behavior and the native format, but it does not disclose whether an existing file is overwritten, whether the path must include the .sldprt extension, or what the tool returns. This is an adequate but incomplete disclosure.

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, front-loaded sentence states the operation, destination format, and rationale with no filler. The parenthetical adds purpose without bloating the description.

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?

For a simple one-parameter save operation the description is broadly adequate, but with no annotations and no output schema it leaves out side effects (e.g., overwrite behavior) and return value or error information. An agent can call it correctly in the common case, but not with full certainty about edge cases.

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?

With 0% schema description coverage, the description is the only source of parameter meaning. It indicates that 'path' is the destination file path and that it should point to a native .sldprt file, which is material information beyond the raw schema. It does not discuss extension handling or paths, but for a single string parameter the key semantics are conveyed.

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 ('Save'), identifies the resource ('the current part') and the exact output ('a native .sldprt file'), and adds the intent ('so it can be reopened/edited'). This clearly differentiates it from export, save_assembly, and other siblings.

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 gives clear context: use this when persisting the current part in a natively editable format. It does not explicitly name alternatives like export or save_assembly or state when not to use them, so it falls short of a 5.

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