disconnect_m365_account

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

No annotations provided; description mentions token removal but lacks details on side effects (e.g., session termination, reversibility, or confirmation needed). This is insufficient for a destructive operation.

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?

Single sentence with no extraneous words, perfectly concise.

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?

Low complexity tool; description covers core purpose. Could mention inverse relationship to connect_m365_account, but not essential.

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, so description adds no parameter info; baseline 4 applies as schema coverage is 100%.

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?

Description uses specific verb 'disconnect' and resource 'Microsoft 365 account' with detail 'remove stored tokens', clearly distinguishing it from sibling tools like connect_m365_account.

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?

Implied usage for disconnecting M365, but no explicit guidance on when to use versus alternatives (e.g., connect_m365_account or disconnect_servicenow) or prerequisites.

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