Disconnect App

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does disclose a significant behavioral trait: 'revoking all connections,' indicating a broad, likely destructive action. However, it does not mention permanence, reversibility, permissions, or other side effects, leaving gaps in the safety profile.

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 a single sentence that front-loads the action and its effect. It is concise, with no wasted words, and includes the critical qualifier 'all connections' without unnecessary elaboration.

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 tool with only one parameter and an output schema, the description is nearly complete. It states the purpose and the key behavioral scope (all connections). However, it could benefit from noting that the action is likely irreversible or requires reconnection, which would enhance completeness given the lack of annotations.

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 input schema covers the single parameter 'integration' with a clear description ('Integration ID or slug to disconnect'), providing 100% schema coverage. The tool description does not add additional semantic meaning beyond what the schema already documents, so a 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 tool's function: 'Disconnect from an integration, revoking all connections.' It uses a specific verb ('disconnect') and resource ('integration'), and explicitly notes the scope ('all connections'), which distinguishes it from sibling tools like list-connections and connect-app.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or reference sibling tools like connect-app or list-connections. The intended context is only implied by the tool's name and description.

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