createSectionCreate a new section in a OneNote notebook by providing the notebook ID and a display name. Use this to organize notes into separate sections.
Create a new section inside a notebook.
| Name | Required | Description | Default |
|---|---|---|---|
| notebookId | Yes | Notebook ID or name. | |
| displayName | Yes | Name for the new section. |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false and destructiveHint=false, but the description adds no extra behavioral context beyond what is already known. It does not mention potential side effects, prerequisites like notebook existence, or uniqueness constraints, providing no added value over the 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?
The description is a single, concise sentence that is front-loaded and contains no redundant information. It effectively communicates the core action and resource.
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 creation tool, the description is adequate but lacks important context such as what happens if the notebook ID is invalid, whether displayName must be unique, or what the response format is. Given the annotations and schema, it is minimally viable but not comprehensive.
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 coverage is 100% with both parameters documented. The description adds little beyond what the schema already provides, only reinforcing that notebookId refers to the parent notebook. Baseline of 3 is appropriate.
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 'a new section inside a notebook', which precisely states the tool's function and differentiates it from sibling tools like createPage.
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 provided on when to use this tool versus alternatives such as createPage or appendToPage. The description simply states the action without context or exclusions, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.