disconnect_m365_account

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

No annotations are provided, so the description carries the full burden. It does disclose one real behavioral trait — the stored sign-in is removed, not just the connection dropped — which is useful for a destructive operation. But it omits whether tokens are revoked, whether re-authentication is possible, and how failures or multiple accounts are handled.

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?

A single front-loaded sentence with no filler. The operation and its consequence are stated in the first clause.

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 destructive, zero-parameter, unannotated tool with no output schema, the description is too thin: it does not state which account is affected when several exist, whether the action is reversible, or what the agent should do beforehand. An agent could invoke this and disconnect the wrong account.

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?

Zero parameters, so there is nothing to document and the schema baseline would normally be 4. However, the absence of any account-selection parameter combined with 'ONE' makes the target ambiguous; the description should clarify that it acts on the default/current account or that a prior listing step 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?

Clear specific verb + resource: 'Disconnects ONE Microsoft 365 account' — an agent can distinguish this from connect_m365_account and from the many sibling *_disconnect tools for other providers. The capitalized 'ONE' signals multi-account awareness, but the tool does not explain how the target account is chosen, leaving a small ambiguity.

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 when-to-use guidance, no preconditions, and no reference to related tools. It does not say whether the agent should first call list_m365_accounts or set_default_m365_account, nor what happens if multiple accounts are connected. The agent must infer all of this.

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