Begin a new handwriting session to capture tablet sketches and notes, preserving previous sessions for later export.
【递纸】开始一个新的手写会话（之前的会话会被保留，可随时导出）。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It does disclose an important behavioral fact: previous sessions are retained and can be exported. However, it does not say what happens to the current active canvas or whether a new session identifier is returned.
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 compact sentence with no filler. The core action is front-loaded, and the parenthetical adds the most relevant behavioral detail without unnecessary length.
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 with no output schema, the description provides the key context an agent needs: starting a new session and reassurance that previous work is preserved. It leaves minor ambiguity about the current canvas state, but this is a low-complexity tool.
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 has zero parameters and schema coverage is 100%, so the description is not required to explain inputs. The baseline of 4 applies because the empty schema fully documents the invocation surface.
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 action and resource: 'start a new handwriting session.' The parenthetical that previous sessions are preserved and exportable makes its behavior distinct from siblings like clear_canvas and export_session, so an agent can identify the right tool.
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?
There is no explicit guidance on when to use this tool versus alternatives. The preservation remark hints at a non-destructive use case, but it does not name when to prefer start_session over clear_canvas, save_snapshot, or list_sessions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.