Microsoft 365 MCP Server

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

No annotations provided, so description carries full burden. Fails to disclose that this terminates the current session, invalidates tokens, or that subsequent API calls will fail until re-authentication. No mention of side effects or return values.

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 concise at 5 words with no filler. Efficiently front-loaded. However, given zero annotations and the stateful nature of authentication, it is slightly too terse to be maximally useful.

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 session management tool with no output schema and numerous account-related siblings (login, select-account, verify-login), the description is minimally adequate but lacks critical context about session termination and authentication state changes.

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?

Input schema has 0 parameters (empty object), establishing baseline 4. Description appropriately does not mention parameters since none exist, and no additional parameter context is needed.

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 specific verb 'Log out' and resource 'Microsoft account'. However, it does not differentiate from sibling 'remove-account', which may imply deleting stored credentials vs. terminating a session. Clarity is good but not exhaustive.

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 'login', 'select-account', or 'remove-account'. No mention of prerequisites (e.g., being logged in) or consequences for subsequent tool calls.

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