fusion_create_sketch

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

The description's 'Create' aligns with readOnlyHint=false and does not contradict any annotation. It adds the useful detail that the sketch is empty, but it does not disclose side effects such as whether a document must be open or whether the new sketch becomes the active target for subsequent sketch tools.

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, front-loaded sentence with no filler or redundant wording. It conveys the essential action, target resource, and parameter semantics efficiently.

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 two-parameter create operation with no output schema, the description is largely complete. The main missing context is the expected working state (e.g., active document) and whether the created sketch becomes active for later geometry tools, but these are not critical to invoking the operation.

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 description clarifies the plane parameter by explaining that xy/xz/yz are base planes and an integer is a construction-plane index, which is meaningful given the anyOf schema. However, it gives no guidance on the 'name' parameter, leaving a gap in an otherwise low-coverage schema.

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 ('Create') with a clear resource ('empty sketch') and location ('base plane (xy/xz/yz) or construction-plane index'). The word 'empty' and the plane focus distinguish this from sibling sketch tools like fusion_create_sketch_on_face and the geometry-drawing tools.

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 implies the usage context: create an empty sketch on a plane before adding geometry. However, it does not explicitly state when to choose this over fusion_create_sketch_on_face or mention any exclusions, so the guidance remains implicit.

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