Connect Instagram

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

The description reveals concrete behaviors beyond the annotations: reuse of a verified saved session, opening a dedicated local Chromium profile, returning immediately with LOGIN_PENDING, and requiring credentials to be entered only on instagram.com. These details significantly enrich the agent's understanding of what happens when invoked.

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 three sentences, front-loaded with the usage condition, and every sentence contributes unique information (when to use, what happens, where credentials go). No redundancy or 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?

Given that the tool has no parameters and an output schema exists (which likely documents the return structure), the description covers all essential contextual aspects: session reuse, browser launch, immediate LOGIN_PENDING, and the required follow-up action with instagram_connection_status. It is complete for a connection-initiating tool.

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 takes zero parameters, so there are no parameter details to add. With 0 params, the baseline is 4, and the description appropriately does not attempt to explain parameters, making it fully sufficient.

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 opens with a specific use case: 'Use this when the user wants to connect Instagram or resume an unfinished local login.' It clearly identifies the resource (Instagram) and the action (connect), and distinguishes itself from sibling tools by noting that the user should 'then use instagram_connection_status' for status checks.

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?

It provides an explicit trigger condition ('Use this when...') and instructs the user to follow up with instagram_connection_status. However, it does not explicitly state when not to use this tool or directly compare with alternatives like instagram_disconnect or instagram_get_non_followers, so it's clear but lacks explicit exclusions.

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