nx_save_part

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action without addressing side effects. It does not say whether the save overwrites an existing file, what happens if no part is active, or whether the operation can fail.

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 one short, front-loaded sentence with no filler. It supplies exactly the needed information for a parameterless command and does not waste tokens.

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 zero-parameter tool, 'Save the active work part' is nearly complete: it names the object and the action. It falls slightly short because it does not specify behavior when no part is active or whether the save is a persistent overwrite, but the output schema can cover result details.

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 properties, so there are no parameter semantics for the description to add. Since there are no parameters, the baseline of 4 applies and the description appropriately references the contextual 'active work part' state.

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') and identifies the exact resource ('active work part'), making the tool's core function clear. It doesn't explicitly name or contrast sibling tools like nx_close_part or nx_release, but the action of saving is distinct enough that an agent can tell it apart.

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 no guidance on when to invoke this tool versus alternatives such as nx_close_part or nx_release. There is no mention of prerequisites (e.g., an active part must exist) or of typical sequences like saving before closing.

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