Finish the active sketch to inspect it or switch to another one. Use when you need to exit sketch editing mode manually.
Finish editing the current sketch. The solid tools do this automatically, so you only need it when you want to inspect a finished sketch or switch to another one.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide idempotentHint=true and destructiveHint=false, covering safety. The description adds context that this command manually terminates sketch-editing mode and is complementary to solid tools, which auto-close. No contradiction with annotations.
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?
Two short sentences, with the primary action and key usage condition front-loaded. No filler or repeated annotation values.
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, no-output-schema tool, the description covers the action, when it is needed, and when it is not. An agent can determine whether to invoke it without consulting additional sources.
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 tool takes zero parameters, so there is no parameter detail the description must supply. Baseline 4 applies for parameterless tools, and the description focuses on the operation rather than inputs.
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 states a specific verb and resource: 'Finish editing the current sketch' – clearly an action to exit sketch-editing mode. It also differentiates from solid tools by noting they do this automatically, so an agent can distinguish manual close from other operations.
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?
It explicitly specifies when manual invocation is needed: 'only need it when you want to inspect a finished sketch or switch to another one.' It also gives the when-not: solid tools close the sketch automatically, so the call is unnecessary in those workflows.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.