Microsoft 365 MCP Server

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

Without annotations, the description carries full burden. It adds critical behavioral context that this only affects local cache, not server-side account deletion. However, it omits side effects (impact on current session, whether re-authentication is required), idempotency, and error conditions.

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 terse at 7 words, with no wasted language. However, given zero annotations and the tool's destructive nature, additional behavioral context would be warranted without adding verbosity.

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?

Minimum viable for a cache-removal tool. Lacks output description (though none exists) and behavioral depth, but the single-parameter schema is fully documented. Adequate but would benefit from explicit mention of relationship to login/logout workflow.

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 ('The account ID to remove'), establishing baseline 3. The description implies the parameter by referencing 'account' but adds no syntax details, format constraints, or examples beyond what the schema provides.

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?

Clear verb ('Remove') and resource ('Microsoft account') with scope constraint ('from the cache'), distinguishing it from server-side deletion tools like 'delete-outlook-contact'. However, it fails to differentiate from sibling 'logout' or explain when to prefer removal over logout.

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 on when to use this tool versus 'logout' or 'select-account', nor prerequisites (e.g., whether the account must not be currently selected). No mention of post-removal steps needed.

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