delete_pagePermanently remove a specific OneNote page using its ID, with no undo. Confirm the page ID before deletion to avoid irreversible data loss.
Permanently deletes a OneNote page by ID. There is no undo — confirm with the user before calling.
| Name | Required | Description | Default |
|---|---|---|---|
| pageId | Yes | OneNote page ID to delete. This action is irreversible. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (idempotentHint and destructiveHint), the description adds critical behavioral context: the deletion is permanent, there is no undo, and user confirmation is required. This is exactly the kind of additional transparency an agent needs for a destructive action.
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 no filler. The most important fact (permanent deletion) is front-loaded, and the actionable guardrail (confirm with user) follows immediately.
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 single-parameter destructive tool with no output schema, the description provides all essential information: what is deleted, that it is irreversible, and that user confirmation is required. Annotations cover safety and idempotency, so nothing critical is missing.
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 input schema has 100% coverage and fully describes pageId, including its irreversibility. The description only says 'by ID', adding little semantic value beyond the schema, so the baseline score 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 states a specific verb and resource: 'Permanently deletes a OneNote page by ID.' This clearly distinguishes it from sibling tools like update_page or copy_page and leaves no ambiguity about what operation is performed.
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 gives a clear and important usage guardrail: 'confirm with the user before calling' and emphasizes that there is no undo. It does not explicitly name alternatives or when-not-to-use conditions, but for a destructive deletion tool the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.