Microsoft 365 MCP Server

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

While annotations confirm readOnly/destructive status, the description adds no behavioral context about pagination defaults, what 'openWorldHint' implies for scope, or how the OData query parameters (filter, expand) behave. Fails to disclose return structure given no output schema exists.

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?

Extremely brief (4 words) which avoids verbosity, but inappropriately minimal given the tool's complexity (11 parameters including OData query options). Front-loaded with the core action but wastes no words because there are no words to waste—undersized for the functionality described.

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?

Inadequate for a complex OData-enabled listing tool with 11 parameters and no output schema. Lacks explanation of what defines a 'notebook object', expected return values, or how to construct valid filter/search queries. Relies entirely on structured metadata without supplemental narrative context.

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 description coverage is 100%, establishing a baseline of 3. The description adds no parameter-specific guidance (e.g., explaining that 'filter' supports OData syntax or how 'fetchAllPages' interacts with 'top'), but meets minimum expectations given comprehensive schema documentation.

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?

States the basic verb (Retrieve) and resource (notebook objects) but lacks specificity regarding OneNote notebook hierarchy (top-level vs sections/pages) and does not distinguish from sibling tools like 'list-onenote-notebook-sections'. Adequate but generic.

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, when to use pagination parameters versus fetchAllPages, or prerequisites such as user authentication. Zero usage context provided.

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