Microsoft 365 MCP Server

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

Annotations declare readOnlyHint=true and destructiveHint=false, covering safety profile. However, the description adds no behavioral context regarding pagination behavior (despite fetchAllPages parameter), OData query capabilities, or what the response contains. No mention of openWorldHint implications.

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?

Single sentence (9 words) is front-loaded with the action verb. However, given the tool's complexity (12 parameters including OData support), the description may be overly terse rather than appropriately concise—missing opportunity to signal advanced query capabilities.

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?

Despite rich input schema with OData support and lack of output schema, description provides only minimal context ('page objects'). Missing: return value structure, pagination behavior explanation, or guidance on leveraging the rich filtering/selection capabilities implied by the parameters.

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 has 100% description coverage, establishing baseline of 3. The description only adds semantic mapping for 'specified section' referencing the required onenoteSectionId, but provides no context for the OData query parameters (top, skip, filter, expand) or the fetchAllPages flag.

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?

Uses specific verb 'Retrieve' and identifies resource 'page objects' and scope 'from the specified section'. Clear distinction from sibling tools like create-onenote-page (creation vs retrieval) and list-onenote-notebook-sections (pages vs sections), though could more explicitly contrast with get-onenote-page-content.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to enumerate pages vs retrieving content of a specific page). No mention of prerequisites beyond the implicit requirement of having a section ID.

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