Microsoft 365 MCP Server

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

While annotations indicate the operation is destructive and not read-only, the description adds no behavioral specifics beyond 'Creates.' It fails to disclose Excel-specific side effects, such as how the chart interacts with existing worksheet data or what occurs if the specified worksheet does not exist.

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 four-word description is inappropriately concise for a six-parameter tool with nested objects and destructive side effects. The extreme brevity constitutes underspecification rather than efficient communication, failing to front-load any critical operational details.

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?

Given the tool's complexity (destructive operation, four required parameters including complex nested objects in 'body', no output schema), the description is dangerously incomplete. It omits Excel-specific context, ignores the nested body structure requirements, and provides no indication of success/failure behavior.

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 83%, triggering a baseline score of 3. The description adds no parameter-specific information, but the schema adequately covers five of six top-level parameters (driveId, driveItemId, etc.). However, the critical 'body' parameter—containing nested chart configuration (type, sourceData, seriesBy)—lacks descriptions in both schema and description.

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 'Creates a new chart' essentially restates the tool name with spaces added, constituting a tautology. It fails to specify the Excel context (despite the tool name), the target worksheet location, or distinguish meaningfully from sibling 'create-*' tools beyond the resource noun.

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 other creation tools, prerequisites for the drive/workbook/worksheet IDs, or what chart types are supported. The description offers zero contextual guidance for the agent's decision-making.

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