onedrive_disconnect

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the effect is a disable-not-delete and that tools stop reading until re-enabled, but the sentence is cut off before finishing where re-enabling happens, leaving the reversibility path incomplete.

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?

There is no filler, but the single sentence is truncated with an ellipsis and never completes its thought, so it fails to deliver a usable, front-loaded definition.

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 zero-parameter disconnect tool with no annotations and no output schema, an agent needs to know exactly what state changes and how to reverse it; the truncated description leaves the reversal path and folder targeting unresolved.

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?

The schema has zero parameters (baseline 4), but the description's claim of acting on 'one OneDrive folder' implies a target selector the input schema does not expose, creating confusion about how a specific folder is identified.

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 verb+resource ('Turns one OneDrive folder off') is specific and the effect ('its tools stop reading it') is stated, but the sentence is truncated mid-clause with '...' and it never resolves which folder, leaving the core action ambiguous relative to the zero-parameter schema.

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?

It notes the action is reversible by the user, which hints at when it applies, but gives no guidance on when to call this versus onedrive_set_scope or per-service disconnect siblings like gdrive_disconnect, nor any prerequisites.

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