Disconnect a social account

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

Annotations declare destructiveHint=true, but the description goes well beyond that by specifying what survives ('already-published posts stay'), what breaks ('anything still scheduled to it will fail'), and the recovery path (user must redo OAuth in the browser). That is precisely the side-effect detail an agent needs before a destructive call.

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?

Three short sentences, front-loaded with the action and immediately followed by consequences. Every sentence carries distinct information with no repetition of the title or schema.

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 destructive, no-output-schema tool, the description covers action, blast radius, irreversibility, and the recovery requirement. Nothing material for correct invocation is missing, and return values are not needed since no output schema exists.

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 100% – both accountId and workspaceId are documented in the schema, including the accountId source ('from list_connected_accounts') and workspaceId defaulting behavior. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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 names a specific verb and resource ('Disconnect a social account from this workspace') and adds the second effect ('revoke the app's access with the platform'), so the agent knows exactly what the call does. No sibling tool performs disconnection, so there is no ambiguity to resolve.

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?

Usage is implied by the consequences spelled out (scheduled posts will fail, OAuth required to reconnect), which helps an agent decide whether to call it. However, there is no explicit when-to-use statement or named alternative, and no prerequisite conditions (e.g. permissions) are given.

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