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

The description discloses that the action cannot be undone and that it removes the account from every scheduled post, which are essential side effects. This aligns well with the destructiveHint annotation and provides sufficient transparency for the user.

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?

The description is concise, using only two sentences with no redundancy. It covers the action, the key consequence, and the irreversible nature without unnecessary detail.

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 delete operation, the description covers the primary effects (account removal and scheduled post removal) and irreversibility. It doesn't address edge cases like non-existent account IDs, but that is not essential for typical use. Overall, the description is complete enough for an agent to understand the tool's purpose and impact.

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 single parameter 'socialAccountId' has its meaning and source fully described in the schema itself ('get from postnitro_list_social_accounts'). The description adds no additional semantic value beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the verb 'disconnect' and the resource 'social account', and explicitly notes that it deletes the account and removes it from scheduled posts, making it unambiguous. It is distinct from list/get operations for social 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?

While it doesn't explicitly name alternatives, the description implicitly guides usage by emphasizing the irreversible nature and the impact on scheduled posts, which are critical warnings for when to use this operation. The sibling tools for listing/retrieving accounts are obvious non-destructive alternatives.

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