proton_disconnect

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

With no annotations, the description carries the full burden. It usefully discloses the concrete mutation (Bridge password removed from the macOS keychain), which implies an irreversible credential purge — good context beyond a bare "disconnect". But it stops there: no statement on whether this is destructive/reversible, whether it affects auth state for other tools, or what happens if no account is connected.

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?

Effect is front-loaded in a single efficient sentence, but the text is truncated mid-word ("from the macO..."), leaving the sentence syntactically broken and the key detail (which credential store) incomplete. A truncated definition is a structural defect, not conciseness.

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-param, no-annotation, no-output-schema mutation tool, an agent still needs to know the blast radius (credential deletion), selection semantics when multiple accounts exist, and success/failure signaling — the description covers only the first and that only partially due to truncation.

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 for the description to disambiguate; baseline 4 applies. One residual ambiguity it does not resolve is *which* account is disconnected when multiple Proton accounts exist, since the tool takes no account identifier.

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?

Specific verb + resource: "Disconnects one Proton Mail account from Local MCP" and it further names the concrete effect (removing the stored Bridge password). An agent can distinguish it from proton_connect / proton_list_emails by name and effect, though the description never explicitly contrasts with those siblings.

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 versus alternatives (proton_connect, other *_disconnect tools, or simply not connecting). No prerequisites, no warning that reconnecting will require re-entering the Bridge password, no mention of what happens to already-fetched mail.

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