Disconnect Instagram

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

Annotations already declare destructive and not read-only. The description adds specific context beyond annotations: it closes Chromium, permanently deletes the profile, and removes locally derived account and relationship data. This clarifies exactly what is destroyed without contradicting annotations.

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?

One concise sentence at 17 words, front-loaded with the main action ('Closes Chromium') and followed by the destructive scope. Every word earns its place with no filler.

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 zero-parameter tool with an output schema, the description adequately covers the side effects (closing Chromium) and the full scope of data deletion. It provides enough information for an agent to decide to invoke it without needing return-value details.

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 tool has zero parameters, and the schema has no properties. The baseline for zero parameters is 4, and the description does not need to add parameter details. No deduction necessary.

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 states a specific action: closes Chromium and permanently deletes the Instagram browser profile plus locally derived account and relationship data. This clearly distinguishes it from siblings like instagram_connect and instagram_get_non_followers, which serve different purposes.

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?

The description does not explicitly state when to use this tool or mention alternatives. The verb 'disconnect' implies usage for disconnecting, but there is no explicit guidance comparing it to connect/status tools. Usage is only implied.

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