nx_create_sketch

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

With no annotations, the description carries the full burden. It does disclose one non-obvious side effect — the new sketch is 'activated' — but omits prerequisites (open part required?), what happens to any previously active sketch, whether a duplicate name is rejected, and whether the operation is undoable.

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 with no filler. It is efficient, though so terse that it omits needed context rather than wasting space.

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?

An output schema exists, so return values needn't be explained. Still, for a state-changing creation tool with zero annotations and zero schema descriptions, the description leaves out prerequisites, naming behavior, and how it fits the sketch workflow.

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 0%, so the description must compensate. 'Principal datum plane' vaguely gestures at the plane parameter but doesn't explain the XY/XZ/YZ choices or the default; the 'name' parameter is never mentioned at all.

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?

Specific verb and resource ('create and activate a sketch') with the placement target ('principal datum plane'). It is reasonably distinguishable from the nx_sketch_* drawing siblings, though it doesn't explicitly state its role as the setup step preceding them.

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 when-to-use guidance and no mention of alternatives or sequencing (e.g., that sketch entities are added afterwards via nx_sketch_line/nx_sketch_rectangle and closed with nx_finish_sketch). Nothing says whether an open part is required.

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