disconnect_account

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description goes further by naming the concrete consequences: the connection is removed, account.disconnected webhooks fire, and Instagram scheduled posts may be transferred to a replacement account. That side-effect detail is unavailable anywhere in the structured fields.

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?

Front-loaded with the action and its destructiveness, then a clearly separated REQUIRED BEFORE CALLING block for the precondition. No filler sentences; each clause carries either a side effect or a gating rule.

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 two-parameter destructive mutation with no output schema, the description covers consequences, the confirmation gate, and the prerequisite discovery call. Nothing an agent needs in order to invoke this safely is 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 coverage is 100% and both parameters are self-documenting, so the baseline is 3. The description adds a small amount by tying confirm to a specific gating workflow ('only after that confirmation') and anchoring account_id to list_accounts, though it largely restates the schema text.

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?

States a specific verb and resource ('Disconnect a connected social account from posterly') and is clearly the inverse of the sibling connect_account. An agent can distinguish it from account-adjacent tools like manage_extra_account or list_accounts without opening a 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?

Gives an explicit precondition sequence: call list_accounts first, surface platform/username/account ID/workspace, obtain explicit user confirmation, then pass confirm=true. This is a when-and-how-to-use rule with no inference required, and the implicit alternative (connect_account) is obvious from the naming.

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