m365_disable_vacation

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that redirect rules are cleared (a destructive side effect) and that the disable is immediate, but it omits permission requirements, reversibility, and whether existing configured out-of-office messages are affected.

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 that states the primary effect and the cleanup action with no wasted words. It is appropriately sized for the tool's scope.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with no annotations and a 0%-documented parameter, the description should cover when to use it, permissions, and the user_upn parameter. These key context pieces are missing.

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 0% and the only parameter, user_upn, is not mentioned in the description. The description does not compensate by explaining the expected format, source, or role of user_upn.

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 states a specific verb ('disables') and resource ('automatic out-of-office replies') plus a secondary effect ('clears temporary vacation redirect rules'), distinguishing it from read sibling m365_get_vacation_status. It does not explicitly name the alternative m365_configure_vacation, so sibling differentiation is implied rather than stated.

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?

The description gives no explicit when-to-use, when-not-to-use, or alternative routing. 'Immediately' hints at urgency but does not say which scenarios call for this tool over m365_configure_vacation or m365_get_vacation_status.

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