Disconnect an account

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

Annotations already flag destructiveHint=true, but the description goes further by specifying exactly what is destroyed (stored token), the additional side effect of revoke=true (removing the app's permissions from the Facebook user), and the downstream impact that scheduled posts stop.

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?

Four short sentences, front-loaded with the core action, then the conditional behavior, the side effect, and the confirmation requirement — no filler or redundancy.

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, zero-required-parameter tool with no output schema, the description covers consequences, conditional behavior, and the confirmation gate. It stops short of stating whether the action is reversible or what must be done to reconnect, which would complete the picture.

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 67% and the undocumented parameter is exactly the one the description explains: revoke=true is tied to Facebook Login permission removal. It adds real meaning beyond the schema, though it does not elaborate on revoke=false beyond the default in the schema.

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 ('Remove a connected account from this server') plus the concrete consequence ('delete its stored token'), which distinguishes it cleanly from siblings like connect_account, complete_connect, and list_accounts.

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 a clear precondition ('Needs the user's confirmation') and clarifies the conditional revoke path, but does not explicitly name the alternative tool (e.g., connect_account) or state when not to use this.

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