nx_create_part

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

With no annotations provided, the description carries the full burden of disclosing side effects and requirements. It only states the action, omitting details such as whether an existing part is overwritten, if a workspace must be configured, or what the response contains. This is insufficient for a mutation operation.

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 a single sentence, which is concise, but it's under-specified rather than appropriately concise. It fails to include essential context, making it more of a placeholder than a useful description. The lack of structure or front-loaded key details reduces its effectiveness.

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 create operation in a CAD environment with an output schema present, the description still omits necessary context like workspace prerequisites, error conditions, or the meaning of the output. It is not complete enough for an agent to call it confidently, especially with no parameter documentation.

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 description coverage is 0%, and the description provides zero information about the 'path' or 'units' parameters. An agent cannot infer what a valid path looks like or how units affect the part creation. This is a critical gap since the schema itself lacks descriptions.

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 the verb 'create' with the resource 'part', clearly stating the action and target. However, it doesn't distinguish itself from sibling creation tools like nx_create_sketch, nor does it clarify what constitutes a 'part' (e.g., a CAD model file). It's specific enough to be understood but lacks differentiation.

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?

No guidance is given on when to use this tool versus alternatives such as nx_open_part or nx_create_sketch. There is no mention of prerequisites like an active workspace or conditions under which this tool is appropriate, leaving the agent to infer usage from the name alone.

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