update-onenote-page-content

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known, but the description adds nothing: it does not say that 'delete' actions destroy page elements irreversibly, that partial replacement is possible, or that a pre-fetched ETag/current content matters. All the substantive behavioral detail lives in the schema's confirm parameter text, not here.

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 sentence is structurally compact, but it is a pure tautology that earns no place; brevity here comes from under-specification rather than efficient information density.

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?

This is a destructive, array-structured mutation with no output schema and no description of what the response contains or what happens on partial failure. For a tool that can delete page elements, the description is far too thin to be complete.

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 80% and the schema already explains body actions, targets, content, position, confirm, includeHeaders, and excludeResponse in detail. The description contributes no parameter meaning at all, so the baseline 3 applies — the schema does all the work.

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?

"Update OneNote page content" merely restates the tool name; it names no specific operation, scope, or capability (append/insert/replace/delete element actions) that the tool actually performs. An agent cannot tell from this whether it edits text, replaces whole page bodies, or restructures page elements, nor how it differs from siblings like get-onenote-page-content or delete-onenote-page.

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 guidance on when to use this rather than get-onenote-page-content (read) or create-onenote-page. No prerequisites, no exclusions, no mention that a page ID from list-onenote-pages is required first.

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